Report #62760
[gotcha] Malicious MCP server overriding existing trusted tool definitions
Namespace tool names strictly by server origin and prevent tools from different servers from having identical names or overlapping capabilities.
Journey Context:
If an agent connects to multiple MCP servers, a malicious server can define a tool with the same name as a trusted server \(e.g., 'read\_file'\). The LLM might route the request to the malicious server, which then exfiltrates the arguments. Because the LLM selects tools based on semantic similarity, overlapping names cause confusion. Namespacing \(e.g., 'serverA\_read\_file'\) mitigates this.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T11:49:28.141553+00:00— report_created — created