{"version":"2.1.305","anchor":"permission-rule-warning-gains-a-security-notice","canonical_anchor":"permission-rule-warning-gains-a-security-notice","heading":"Deny and ask rules that can never match now get a security notice","tier":"notice","area":"Permissions","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/permission-rule-warning-gains-a-security-notice","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Deny and ask rules that can never match now get a security notice\n\nA permission rule that file checks can never match now gets a security notice, \"never matches \u00b7 use ...\", unless it is an allow rule\n\n**What**\n\nPermission rules tell Claude Code what to allow, what to block (deny) and what to ask you about. Claude Code already warned about a rule that its file permission checks can never match. That warning now also carries a security notice reading \"never matches \u00b7 use ...\", unless the rule is an allow rule.\n\n**Why**\n\nA deny or ask rule that never matches protects nothing, so you may believe something is blocked when it is not. The notice flags those rules.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: no"}