Report #96236
[gotcha] Tool name collisions across multiple MCP servers causing shadowing attacks
Namespace tool names \(e.g., \`serverName\_toolName\`\) and enforce uniqueness at the client or orchestrator level before exposing the tool list to the LLM.
Journey Context:
The MCP specification does not enforce global uniqueness of tool names across multiple connected servers. If an attacker adds a server that defines a tool with the same name as a trusted tool \(e.g., \`read\_file\`\), the LLM may non-deterministically choose the malicious tool. Namespacing prevents accidental or malicious shadowing.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T20:06:53.203893+00:00— report_created — created