{"version":"2.1.318","anchor":"mcp-tools-whose-names-collide-get-a-toolnameshared-flag-and","canonical_anchor":"mcp-tools-whose-names-collide-get-a-toolnameshared-flag-and","heading":"Allow rules no longer apply to MCP tools that end up with the same name","tier":"notice","area":"Permissions","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/mcp-tools-whose-names-collide-get-a-toolnameshared-flag-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Allow rules no longer apply to MCP tools that end up with the same name\n\nWhen two tools from one MCP server get the same name in Claude Code, allow rules are refused for them with a warning, and connector servers are labelled\n\n**What**\n\nMCP servers are outside services that give Claude extra tools. An allow rule is a setting that lets a tool run without asking you first. Sometimes two tools from the same server end up with the same name inside Claude Code. These changes handle that case:\n\n- `toolNameShared`: a new value passed when an MCP tool is built. It is true when an experiment-gated check holds and the tool's full name is used by more than one tool.\n\n- Allow rules refused: for those tools, allow rules are not applied, including an allow rule for the whole tool. The warning reads: `Allow rules do not apply to \"...\": another tool of this server gets the same name in Claude Code. To use allow rules, the server must rename one of them.`\n\n- Exact match first: a helper that looks tools up now prefers a tool whose name matches exactly.\n\n- Server details: the stored MCP information now records `serverProvenance` and `serverUrl`. Connector servers are marked with `serverProvenance: \"connector\"`.\n\nOne finding also noted smaller, unrelated changes. Branch-point diffs now return `noDiffReason` values such as \"root-moved\" and \"diff-failed\". Uploads accept an `onRejectedPastScreen` callback. The ccs sender-address helper also sets a country header value.\n\n**Why**\n\nBefore, an allow rule could apply to the wrong tool when two tools shared a name. Now neither tool gets the allow rule until the server renames one of them, so you are asked before either one runs.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: yes"}