Distinguish tool auto-approval from tool availability

Verify that allowed_tools pre-approves listed tools and use disallowed_tools to block explicit exclusions.

Goal

Avoid confusing “auto-approved” with “only these tools are available” when configuring tool permissions.

Set allowed_tools=[...] in ClaudeAgentOptions, listing only tools that may be auto-approved. [readme]
Use disallowed_tools=[...] for tools that must be blocked; other unlisted tools may still be decided by permission_mode or can_use_tool. [readme]
Verify allow/deny behavior with a read-only probe in a test directory, then enable write tools one at a time. [readme]

Confirm blocked tools are explicitly in disallowed_tools and unapproved tools follow the expected permission path.

If a tool remains callable, check whether it was merely omitted from allowed_tools; omission does not disable it.

Start with read-only tools; authorize any write or command execution separately.

CLI configuration and permission_mode also affect tools; this list alone is not a filesystem or network sandbox.

These values describe the upstream repository, not popularity or likes for an individual skill or playbook.

No metrics snapshot is available yet.

License: MIT