If you connect an AI coding assistant to local tools today, you probably rely on the Model Context Protocol (MCP). By default, MCP clients connect directly to tools declared in local settings files API Evangelist on MCP . A developer adds a command to their editor config, and the agent starts invoking that tool.
That quick setup creates an immediate trust boundary problem. When a developer registers a tool using the stdio transport, the MCP client spawns a local subprocess inheriting the user's OS permissions, environment variables, and network access Yobitel MCP Architecture .
If someone pulls an unvetted package from a public registry, any dependency compromise allows code execution inside the developer's shell Glama on MCP Security . Long-lived corporate credentials frequently end up hardcoded into workstation configuration files TrueFoundry on MCP credentials .…