{"version":"2.1.296","anchor":"mcp-tool-permission-analytics-gain-org-ask-ceiling-reason-co","canonical_anchor":"mcp-tool-permission-analytics-gain-org-ask-ceiling-reason-co","heading":"Usage data now records when an organization limit caps an MCP tool at ask","tier":"internal","area":"Telemetry","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/mcp-tool-permission-analytics-gain-org-ask-ceiling-reason-co","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Usage data now records when an organization limit caps an MCP tool at ask\n\nPermission records for MCP tools now carry a reason code when the server's highest allowed permission is ask\n\n**What**\n\nMCP servers are add-ons that give Claude Code extra tools. When Claude Code decides whether one of those tools may run, it sends a usage record about the decision. If the decision came from a rule, or from one particular other reason, and the MCP server's highest allowed permission is \"ask\", the record now carries the reason code `org_ask_ceiling`.\n\n**Why**\n\nThis only changes what is reported. It points to an organization-level limit that keeps MCP tools at asking for approval rather than running freely.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}