Skip to content
BENIBIX Learn

--tools vs --allowedTools

People think --allowedTools limits Claude to the tools it lists. It does not. --allowedTools only says which tools may run without asking you first. Every other tool is still there and can ask. --tools is the one that decides which built-in tools exist at all, and anything it leaves out is gone. To lock a session down, use --tools. To stop it asking about safe tools, use --allowedTools.

AI⌨️ Claude Code

--tools Flag

It sets which built-in tools Claude has in a session.

--tools sets which built-in tools Claude has in this session. Name them, such as "Bash,Edit,Read", and the rest are gone. An empty "" turns all of them off, and "default" gives the normal set. It does not touch MCP tools. To take those away too, add --disallowedTools "mcp__*".

Example
Lucy wants a review that cannot change any file. She starts with --tools "Read,Grep,Glob", so Claude has no Edit or Bash to use.
Why it matters
A tool that is not there cannot be misused, however the prompt is worded.
Full entry
AI⌨️ Claude Code

--allowedTools Flag

It lists tools that run without asking you first.

--allowedTools lists tools that run without asking you first. Each entry is a permission rule, such as Read or "Bash(git log *)". Tools you leave off still exist, they just ask before they run. To take a tool away, use --tools or --disallowedTools. --allowed-tools is the same flag.

Example
Jack's CI job only needs git log and file reads. He lists just those in --allowedTools, so the job never stops to ask about them.
Why it matters
A run with no one watching cannot answer a prompt. The allow list keeps it moving.
Full entry

In one line

--tools Flag
It sets which built-in tools Claude has in a session.
--allowedTools Flag
It lists tools that run without asking you first.