Under the hood
MCP tool permission checks now first ask an SDK-level permission hook before falling back to normal consent logic
What
When 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.
Why
This 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.