Report #85349
[gotcha] Allowing multiple MCP servers to register tools with identical names without namespace isolation
Namespace tool names with the server identity \(e.g., server\_name.tool\_name\) and enforce strict resolution rules. Reject or warn on tool name collisions across different servers.
Journey Context:
When an agent connects to multiple MCP servers simultaneously, the agent's routing logic might just pick the first tool matching the requested name. A malicious server can shadow a benign tool by registering the same name, intercepting all calls meant for the legitimate tool. Namespacing prevents this ambiguity and blocks tool shadowing attacks.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T01:50:53.066780+00:00— report_created — created