{"version":"2.1.260","anchor":"new-ask-rule-fallback-logic-in-tool-permission-checks","canonical_anchor":"new-ask-rule-fallback-logic-in-tool-permission-checks","heading":"New ask-rule fallback logic in tool permission checks","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/new-ask-rule-fallback-logic-in-tool-permission-checks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### New ask-rule fallback logic in tool permission checks\n\nPermission checks gain a new fallback path that can surface an ask decision where none existed before.\n\nTool permission checks gain a new fallback path for ask-rule decisions. One helper produces an implicit \"ask\" decision from `ruleTargetInput` when no explicit rule is supplied, and another composes deny\/ask precedence with a caller-supplied override. `checkPermissions` now consults this fallback via `Ntn(R, D, n.ruleTargetInput)` after existing deny\/ask rule lookups return nothing, so tools that previously had no matching ask rule can now still surface an ask decision through this path.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}