{"version":"2.1.311","anchor":"tool-permission-prompt-text-distinguishes-cli-owned-mcp-tool","canonical_anchor":"tool-permission-prompt-text-distinguishes-cli-owned-mcp-tool","heading":"Approval prompts for Claude Code's own MCP tools give a clearer reason","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/tool-permission-prompt-text-distinguishes-cli-owned-mcp-tool","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Approval prompts for Claude Code's own MCP tools give a clearer reason\n\nWhen a tool that Claude Code itself provides must always be approved, the prompt now says \"Claude Code asks before every use of this tool.\"\n\n**What**\n\nMCP tools are tools added by outside programs called MCP servers. Some MCP tools are set to always ask for your approval before running. When such a tool is one that Claude Code itself provides, the approval prompt now gives this reason: \"Claude Code asks before every use of this tool.\"\n\nOther MCP tools set to always ask keep the reason they showed before. Previously every one of these tools showed the same reason.\n\n**Why**\n\nThe prompt now tells you that the request to approve comes from Claude Code itself, not from a setting of yours.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}