{"version":"2.1.323","anchor":"org-ask-ceiling-decision-code-extended-to-connector-limits","canonical_anchor":"org-ask-ceiling-decision-code-extended-to-connector-limits","heading":"Organization ask limit now covers the connector behind a tool","tier":"internal","area":"Permissions","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/org-ask-ceiling-decision-code-extended-to-connector-limits","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Organization ask limit now covers the connector behind a tool\n\nThe org_ask_ceiling reason now also applies when the connector behind a request is limited to ask, or its limit could not be read\n\n**What**\n\nWhen a request for permission is shaped by an organization's limits, Claude Code records a reason code. The description of `org_ask_ceiling` now covers two more cases besides an MCP tool's own limit being set to ask:\n\n- the limit on the connector behind the request is set to ask\n\n- that limit could not be read\n\n**Why**\n\nOrganization limits on connectors can now force Claude Code to ask before using their tools, including when the limit itself cannot be read.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}