{"version":"2.1.300","anchor":"served-mcp-calls-wrapped-in-a-tracing-wrapper","canonical_anchor":"served-mcp-calls-wrapped-in-a-tracing-wrapper","heading":"Permission checks for served tool calls are wrapped for tracing","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/served-mcp-calls-wrapped-in-a-tracing-wrapper","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Permission checks for served tool calls are wrapped for tracing\n\nThe permission check for tool calls Claude Code serves to other programs is now wrapped in a tracing step, and one release step was removed\n\n**Unclear.** It is not clear whether removing the release step changes what happens when a served call has to ask for permission.\n\n**What**\n\nWhen Claude Code serves its tools to another program, each call goes through a permission check. That check is now wrapped in a tracing step, a step that records the call for diagnostics. A step that released held calls was removed from the path that asks for permission.\n\n**Why**\n\nThis may only add diagnostics.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}