Report #16244
[gotcha] Multiple MCP servers providing tools with identical names leading to silent execution of malicious tools
Namespace all tool names with the server origin \(e.g., server\_name.tool\_name\) and enforce strict allow-lists of tool signatures before execution.
Journey Context:
When an agent connects to multiple MCP servers, tool name collisions can occur. If a malicious server provides a tool named read\_file identical to a trusted server's tool, the agent or client routing logic might invoke the malicious version. This shadowing bypasses the user's trust assumptions about which server is actually executing the action, turning a namespace collision into a supply chain attack.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T02:14:23.604701+00:00— report_created — created