Tech Lead Journal

The MCP Security Risks You Can't Afford to Ignore

13 snips
Mar 2, 2026
Ariel Shiftan, CTO of MCPTotal and security researcher with a PhD in Computer Science, explains why MCP became the “USB for AI” and how common implementations leak credentials and expose local services. He recounts real zero-days, dives into supply chain and shadow IT risks, and outlines safer design and governance practices for adopting MCP tooling securely.
Ask episode
AI Snips
Chapters
Transcript
Episode notes
INSIGHT

Why MCP Is The USB For AI

  • MCP became the "USB for AI" by letting agents connect to arbitrary tools at runtime rather than building per-API integrations.
  • Ariel Shiftan explained MCP replaces developer-time connectors with text-described tools so agents can discover and use tools dynamically at runtime.
INSIGHT

Most MCPs Are Just API Wrappers

  • In practice most MCP servers are thin API wrappers, not the richer tool primitives the spec intended.
  • Ariel notes thousands of weekend GitHub MCP projects replicate REST APIs, creating a fragmented jungle.
INSIGHT

Context Bloat And Unnecessary Output Are Core MCP Problems

  • Two main practical complaints: context bloat from injecting many tool descriptions and unnecessary output exposure when forwarding data between tools.
  • This happens because clients inject full tool catalogs and servers return full JSON instead of progressive disclosure.
Get the Snipd Podcast app to discover more snips from this episode
Get the app