{"version":"2.1.269","anchor":"deny-by-rule-tool-responses-now-carry-an-explicit-deniedbype","canonical_anchor":"deny-by-rule-tool-responses-now-carry-an-explicit-deniedbype","heading":"Deny-by-rule tool responses now carry an explicit deniedByPermissionRule flag","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/deny-by-rule-tool-responses-now-carry-an-explicit-deniedbype","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Deny-by-rule tool responses now carry an explicit deniedByPermissionRule flag\n\nEdit-tool permission denials now carry an explicit `deniedByPermissionRule` flag used to trigger a callback\n\n**What**\n\nWhen the Edit tool is denied by a permission rule, whether through the 'ask' or 'deny' behavior, the response now includes a `deniedByPermissionRule: true` field alongside the existing denial message and error code. This flag is read downstream to trigger an `onPermissionDenial` callback.\n\n**Why**\n\nThis lets other parts of Claude Code specifically detect and react when an edit was blocked by a permission rule, rather than only having a generic denial message to work with.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}