Tool 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.
New ask-rule fallback logic in tool permission checks
Permission checks gain a new fallback path that can surface an ask decision where none existed before.
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PermissionsArea: what it touches
ImprovementsKind: in v2.1.260,
ImprovementsSection of the release