{"version":"2.1.265","anchor":"mcp-tool-checkpermissions-now-consults-an-sdk-level-permissi","canonical_anchor":"mcp-tool-checkpermissions-now-consults-an-sdk-level-permissi","heading":"MCP tool checkPermissions now consults an SDK-level permission hook first","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/mcp-tool-checkpermissions-now-consults-an-sdk-level-permissi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### MCP tool checkPermissions now consults an SDK-level permission hook first\n\nMCP tool permission checks now first ask an SDK-level permission hook before falling back to normal consent logic\n\n**What**\n\nWhen Claude Code decides whether an MCP tool is allowed to run, it now first checks whether the SDK layer has already made a decision. If it has, that decision is used directly; otherwise Claude Code falls through to its usual suggestion and consent flow.\n\n**Why**\n\nThis lets a higher-level permission decision (for example, one set by an SDK integration) take priority over Claude Code's default prompt-for-consent behavior for MCP tools.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}