{"version":"2.1.260","anchor":"argument-scoped-permission-rules-for-built-in-tool-controls","canonical_anchor":"argument-scoped-permission-rules-for-built-in-tool-controls","heading":"Argument-scoped permission rules for built-in tool controls","tier":"use","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/argument-scoped-permission-rules-for-built-in-tool-controls","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Argument-scoped permission rules for built-in tool controls\n\nPermission rules can now target specific arguments like Bash(curl *) instead of whole tools.\n\n`builtinToolPolicy` and `disabledBuiltinTools` now accept argument-scoped rules like `Bash(curl *)` or `Read(**\/secrets\/**)`, not just bare tool names. New parsing and validation logic, `parseBuiltinRule` and `canonicalBuiltinRule`, backs this and warns on malformed entries.\n\n- Area: Permissions\n- Names: `builtinToolPolicy`, `disabledBuiltinTools`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5"}