{"version":"2.1.305","anchor":"tools-typo-warnings-now-also-surface-as-securitywarnings","canonical_anchor":"tools-typo-warnings-now-also-surface-as-securitywarnings","heading":"Mistyped --tools exclusions now also produce short security warnings","tier":"use","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/tools-typo-warnings-now-also-surface-as-securitywarnings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Mistyped `--tools` exclusions now also produce short security warnings\n\nA `--tools` exclusion that matches no built-in tool, or a bare prefix with no tool name, now also produces a short security warning\n\n**What**\n\nThe `--tools` flag is an option you add to the `claude` command to limit which built-in tools Claude can use. Claude Code already gave a long warning when part of that list looked wrong. It now also produces a separate list of short security warnings for these cases:\n\n- An exclusion in `--tools` that matches no built-in tool, with a message ending \"matches no tool \u00b7 check for typos\"\n\n- A bare prefix with no tool name after it\n\nThe permission setup, which decides what Claude is allowed to do, also returns its own short security warnings, such as \"rule never matches\" for a permission rule that can never apply.\n\n**Why**\n\nThe messages are short enough for a compact display, so a mistyped exclusion is easier to spot. A typo there can mean a tool you meant to block is still available.\n\n- Area: Permissions\n- Names: `--tools`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}