{"version":"2.1.281","anchor":"mcp-insufficient-scope-error-now-carries-the-required-scope","canonical_anchor":"mcp-insufficient-scope-error-now-carries-the-required-scope","heading":"MCP insufficient_scope error now carries the required scope","tier":"internal","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/mcp-insufficient-scope-error-now-carries-the-required-scope","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### MCP insufficient_scope error now carries the required scope\n\nWhen an MCP server rejects a tool call for missing permissions, the error now also records which scope was needed\n\n**Unclear.** The finding does not say what uses the stored scope once it is attached to the error.\n\n**What**\n\nMCP servers are add-ons that give Claude extra tools. A server can reject a tool call with `insufficient_scope`, which means your login does not grant enough access. When that happens, the error Claude Code raises now also stores the scope the server asked for. A scope is a named permission.\n\nThe message you see was already there before: it says the server needs additional permissions, names the scope, and tells you to run `\/mcp` to sign in again.\n\n**Why**\n\nThe required scope now travels with the error itself, not only inside the text of the message. To fix the error, run `\/mcp` and sign in to that server again.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}