{"version":"2.1.318","anchor":"permission-prompt-tool-gets-a-new-refusal-reason-for-ambig","canonical_anchor":"permission-prompt-tool-gets-a-new-refusal-reason-for-ambig","heading":"Clearer error when two tools on one MCP server end up with the same name","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/permission-prompt-tool-gets-a-new-refusal-reason-for-ambig","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Clearer error when two tools on one MCP server end up with the same name\n\n`--permission-prompt-tool` now explains when it cannot approve an MCP tool because another tool on the same server gets the same name\n\n**What**\n\n`--permission-prompt-tool` names an MCP tool that answers permission prompts when Claude Code runs without you watching. Claude Code now gives a specific reason when that tool cannot approve a tool because another tool on the same MCP server ends up with the same name inside Claude Code. The message says the server must rename one of the two tools.\n\n**Why**\n\nIf approval fails because of a tool name clash within one server, you now get a clear message and a fix instead of no specific explanation.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}