MCP
MCP tool poisoning is an attack where a malicious MCP server hides instructions in a tool's description, which the model reads but the user usually never sees.
MCP tool poisoning is an attack where a malicious MCP server hides instructions in a tool's description, which the model reads but the user usually never sees. Invariant Labs disclosed it in April 2025 using an innocent-looking add tool whose hidden description told the agent to read ~/.cursor/mcp.json and ~/.ssh/id_rsa and pass their contents back through a tool argument. Related variants include rug pulls, where a server changes a tool description after the user approved it, and tool shadowing, where one server's description changes how the agent uses another server's trusted tools. Suggested mitigations include showing users the full tool descriptions and pinning server versions.
Primary source: invariantlabs.ai
Example
In practice, developers reach for MCP Tool Poisoning when they need the capability described above as part of an AI feature or workflow.
Hands-on guides, comparisons, and tutorials that cover MCP.
FAQ
MCP tool poisoning is an attack where a malicious MCP server hides instructions in a tool's description, which the model reads but the user usually never sees.
MCP Tool Poisoning sits in the MCP part of the AI stack. Understanding it helps you make better decisions when building, debugging, and shipping AI features.
Developers Digest publishes tutorials and videos that cover MCP topics including MCP Tool Poisoning. Check the blog and YouTube channel for hands-on walkthroughs.
Related
A function exposed by an MCP server that an AI agent can call to perform an action.
MCP authorization is the part of the Model Context Protocol spec that defines how a client gets permission to call a protected MCP server over an HTTP-based transport.
An application that connects to MCP servers to use the tools, resources, and prompts they expose.

New tutorials, open-source projects, and deep dives on coding agents - delivered weekly.