{"version":"2.1.310","anchor":"mcp-permission-check-handles-refused-legacy-grants","canonical_anchor":"mcp-permission-check-handles-refused-legacy-grants","heading":"MCP tool permission check now accounts for refused legacy access grants","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/mcp-permission-check-handles-refused-legacy-grants","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### MCP tool permission check now accounts for refused legacy access grants\n\nThe permission check for MCP tools now reacts when an older-style access grant was refused, for plugin servers or failed owner checks\n\n**Unclear.** It is not clear whether a refused legacy grant now blocks the tool, asks for approval, or something else.\n\n**What**\n\nMCP servers are add-ons that give Claude extra tools. Claude Code checks whether each MCP tool is allowed to run. That check now also responds when an older-style access grant has been refused. It does this when the server comes from a plugin, or when the older ownership check fails.\n\nA separate check now also picks out servers that are not set up through claude.ai and whose names start with a particular prefix.\n\n**Why**\n\nThis tightens how older MCP access grants are honoured.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}