{"version":"2.1.323","anchor":"tool-calls-refused-by-a-permission-rule-get-a-permission-ru","canonical_anchor":"tool-calls-refused-by-a-permission-rule-get-a-permission-ru","heading":"Actions blocked by a permission rule are now labelled as such","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/tool-calls-refused-by-a-permission-rule-get-a-permission-ru","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Actions blocked by a permission rule are now labelled as such\n\nA tool call refused by one of your permission rules is now given the reason \"permission-rule\" instead of no reason\n\n**What**\n\nA tool call is one action Claude takes, such as editing a file or running a command. Permission rules are settings that allow or block such actions. When a permission rule refuses a tool call, Claude Code now records the reason as `permission-rule`. Before, these refusals were recorded with no reason. Logs now also include the parts of a result marked as refused.\n\n**Why**\n\nRefusals caused by your rules can now be told apart from actions that were interrupted, both in usage reporting and in tool results.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}