Use enforceable tool policies rather than relying on prose instructions as access controls.
Coding & development · Documented · Documentation checked 2026-10-04
Claude Code in terminals and supported development surfaces; Claude chat is not a local shell.
Authentication, installed version, surface, subscription or API billing, and organization policy matter.
The worked example is illustrative and has not been tested in a signed-in product account.
What it does and how it connects
Use enforceable tool policies rather than relying on prose instructions as access controls.
Permission rules control tools outside the prompt. The documented precedence is deny, then ask, then allow. Modes such as planning or edit acceptance alter behavior; broad bypass modes are inappropriate for a learning exercise. CLAUDE.md guidance is not the enforcement layer.
Walkthrough
Use the product named in the access panel. The steps below combine documented controls with the editorial example.
- Use the documented permission controls and inspect existing allow / ask / deny rules.
- Choose a mode suited to inspection before making edits.
- Allow a narrowly required operation and keep sensitive tools denied or reviewed.
- Test a harmless permitted request and an explicitly denied operation.
Worked example
Let an agent inspect a sample repo and propose a patch, while withholding external writes. Review any command that installs dependencies or accesses a service. A denied action should end or reshape the task, not trigger a workaround that widens authority.
Inspect this sample repository and propose the fix. Preserve the configured permission boundaries. If a tool is denied or needs approval, explain the operation and pause at that boundary. Do not use an alternate tool to perform a prohibited action.
Inspect and verify the result
Inspect effective settings and actual approval / denial results. Confirm that the correct repository and account are in scope. Test policy with synthetic operations rather than deleting a useful file.
Limits and troubleshooting
Modes and automatic classification differ by version and product surface. Prose reminders do not enforce a deny rule. If a task repeatedly requests unnecessary access, narrow the task instead of enabling bypass.
Data, permissions, and actions
The runtime and connected services enforce different layers of authority. Permission expansion can expose files, networks, and accounts. Review each change and retain enough activity information to understand actions without recording secrets.
Related reading
Local repository work and review
Give a coding agent a reproducible problem and review its actual edits and test output.
A local change with explicit permission review
Implement a small sample fix and verify its behavior.
A read-only extension-assisted review
Use approved issue context and delegated review without external side effects.
Permissions and meaningful approvals
Decide what a system may read, what it may change, and when someone needs to authorize a concrete action.
Sources and verification
Documentation checked 2026-10-04. Examples are illustrative unless described otherwise.
Configure permissions · Anthropic