Secrets lockout generator

Tick the files you don't want Claude Code to read, and get the permissions.deny rules to paste into its settings file.

Nothing leaves your browser. This page makes no network requests. Deny rules are a safety net, not a vault. They stop Claude's own file tools reliably, but the Bash rules only match the command patterns they list, so a determined command (or a script Claude writes) can get round them. The strongest protection is to keep secrets out of the project folder, and to turn on Claude Code's sandbox.

Your settings

Where it goes

.claude/settings.local.json in your project: just for you, and Claude Code keeps it out of git. This is the one I use.
.claude/settings.json in your project: shared with everyone who uses the repo.
~/.claude/settings.json: applies to every project on your machine. Best for things like ~/.ssh and ~/.aws.

If the file already has a permissions.deny list, add these lines to it instead of pasting a second one. Start a new Claude Code session afterwards so the rules load.

Check it works

Ask Claude to read one of the protected files. It should be refused. If it reads the file anyway, check the file path and the JSON for a typo, because a broken settings file is easy to miss.

If a real secret has already been read by an AI tool, treat it as exposed and rotate it. A deny rule only helps from now on.