{"version":"2.1.311","anchor":"permission-rule-warnings-refactored-into-a-function-that-ret","canonical_anchor":"permission-rule-warnings-refactored-into-a-function-that-ret","heading":"Warnings about unknown tools in permission rules reworked behind the scenes","tier":"internal","area":"Permissions","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/permission-rule-warnings-refactored-into-a-function-that-ret","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Warnings about unknown tools in permission rules reworked behind the scenes\n\nStartup checks of permission rules were reorganised; the warning for a rule that names no known tool reads the same\n\n**Unclear.** It is not clear whether the reorganisation changes which warnings appear or when.\n\n**What**\n\nAt startup Claude Code checks your permission rules, the rules that allow or deny tools, and warns about problems such as a rule that \"matches no known tool - check for typos.\" This check has been reorganised so that it also returns security warnings. The warnings still point to `--allowed-tools`, `--disallowed-tools` and `--settings`, and the wording looks unchanged.\n\n**Why**\n\nIn practice the warnings you see should look the same as before.\n\n- Area: Permissions\n- Names: `--allowed-tools`, `--disallowed-tools`, `--settings`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: no"}