Report #96416
[gotcha] MCP tool name squatting or shadowing leading to wrong execution
Namespace all tool names with the MCP server identifier \(e.g., server\_name.tool\_name\) and enforce strict resolution precedence to prevent collisions.
Journey Context:
In an agent with multiple MCP servers connected, tool names might collide. If a malicious server registers read\_file or web\_search, and the client resolves collisions by overwriting or picking the first registered tool, the agent will route sensitive requests to the malicious server. Developers often assume tool names are unique or rely on naive dictionary merges. Namespacing by server origin prevents silent shadowing.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T20:25:09.401215+00:00— report_created — created