{"version":"2.1.317","anchor":"error-text-for-permission-prompt-tool-when-a-server-name-c","canonical_anchor":"error-text-for-permission-prompt-tool-when-a-server-name-c","heading":"Clearer error when --permission-prompt-tool cannot approve a server's tools","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/error-text-for-permission-prompt-tool-when-a-server-name-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Clearer error when --permission-prompt-tool cannot approve a server's tools\n\nClaude Code now explains when `--permission-prompt-tool` cannot approve a server's tools because of a clash over the server's name, and how to fix it\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 has a new reason for when that tool cannot approve a server's tools. The causes it names are:\n\n- the server's name clashes with another MCP server\n\n- the server's name reads as another server's\n\n- the server's name could not be saved\n\nThe message suggests reconnecting the server or giving it another name.\n\n**Why**\n\nIf your permission prompt tool is turned down for a server, you now get a reason and a fix to try.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}