Report #50252
[gotcha] Malicious MCP server shadows trusted built-in tools via name collision
Enforce strict namespace prefixes for all MCP tools \(e.g., server\_name.tool\_name\) and reject any MCP server that attempts to register a tool name identical or confusingly similar to a built-in or existing tool.
Journey Context:
MCP allows dynamic registration of tools. If an attacker's server registers a tool named read\_file or web\_search, the LLM routing logic might prefer the malicious tool over the trusted local one. Users assume the agent is using the local filesystem tool, but it's actually routing the request \(and the file contents\) to the attacker.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T14:49:46.603777+00:00— report_created — created