Documentation 2026-01-24 03:29 UTC to 2026-01-25 03:34 UTC

85 85 

86Permission rules use the format: `Tool` or `Tool(optional-specifier)`86Permission rules use the format: `Tool` or `Tool(optional-specifier)`

87 87 

88A rule that is just the tool name matches any use of that tool. For example, adding `Bash` to the allow list allows Claude Code to use the Bash tool without requiring user approval. Note that `Bash(*)` does **not** match all Bash commands. Use `Bash` without parentheses to match all uses.88A rule that is just the tool name matches any use of that tool. For example, adding `Bash` to the allow list allows Claude Code to use the Bash tool without requiring user approval. `Bash(*)` is equivalent to `Bash` and can be used interchangeably.

89 89 

90<Note>90<Note>

91 For a quick reference on permission rule syntax including wildcards, see [Permission rule syntax](/en/settings#permission-rule-syntax) in the settings documentation.91 For a quick reference on permission rule syntax including wildcards, see [Permission rule syntax](/en/settings#permission-rule-syntax) in the settings documentation.

203| `WebFetch` | Matches **all** web fetch requests |203| `WebFetch` | Matches **all** web fetch requests |

204| `Read` | Matches **all** file reads |204| `Read` | Matches **all** file reads |

205 205 

206<Warning>206`Bash(*)` is equivalent to `Bash` and matches all Bash commands. Both syntaxes can be used interchangeably.

207 `Bash(*)` does **not** match all Bash commands. The `*` wildcard only matches within the specifier context. To allow or deny all uses of a tool, use just the tool name: `Bash`, not `Bash(*)`.

208</Warning>

209 207 

210#### Using specifiers for fine-grained control208#### Using specifiers for fine-grained control

211 209