Check your Claude Code settings.json

Paste your settings and see what Claude Code may do without asking: allow rules that let in any command, rules that never take effect, secrets nothing guards and modes that skip the questions. Then copy the file back with the fixes you pick. Nothing leaves this page.

1Paste your settings file

Which file is it?

Everything runs in this page and nothing you paste is sent anywhere. There is no share link on purpose: settings can hold keys. Values in env are never shown, only their names.

2What it lets through

  • 5 risks
  • 6 checks
  • 3 tips
  1. RiskDoes what can't be undone, without asking

    Bash(git *)

    What it does can't be taken back from your terminal: deleted files, pushed commits, changed cloud resources or databases. Covers git reset, git clean.

  2. RiskReaches other machines without asking

    Bash(curl:*)

    It reaches other machines, so files and keys this session can read can be sent anywhere, and a downloaded script can be run. Covers curl.

  3. RiskRuns any program without asking

    Bash(python3 *)

    It starts whatever program or code follows it, so this one rule allows any command at all. Covers python3, python3 -c.

  4. RiskEdits anywhere, unasked

    Edit

    Claude Code can change files outside the project without asking, such as your shell profile, which runs the next time you open a terminal. Limit it to the project with Edit(./**).

  5. RiskA secret is written into the settings

    env: OPENAI_API_KEY

    A shared .claude/settings.json is checked into git, so everyone with the repository has these values. Use apiKeyHelper or the shell's own environment instead. The checker never shows the values.

  6. CheckThis deny rule does not match what it seems to

    mcp__github__delete_repository(*)

    MCP rules are written mcp__server or mcp__server__tool, with no brackets and no spaces. Claude Code skips this one.

  7. CheckEvery web page is fetched without asking

    WebFetch

    Any page can carry instructions written for the model, and a URL can carry your data out in its query string. Allow the domains you use, such as WebFetch(domain:docs.python.org).

  8. CheckA whole MCP server is allowed

    mcp__github

    Every tool of this server runs without asking, including tools the server adds later. Allow the tools that only look things up by name. The tool risk checker sorts a server's tools for you.

  9. CheckAny project's MCP servers start unasked

    enableAllProjectMcpServers: true

    Every server in a repository's .mcp.json starts without asking you first, so a cloned repository can bring its own tools. Approve servers by name with enabledMcpjsonServers.

  10. CheckNothing keeps Claude Code out of .env

    Read(./.env)

    No deny or ask rule covers .env, so Claude Code reads it like any other file, and its keys can end up in the conversation. A Read deny rule also stops cat, head and tail on the file in commands Claude Code can read.

  11. CheckEdit, then run: an allowed test runs whatever was written

    Bash(npm run *)

    Tests, builds and package scripts run code from the project, and Claude Code may also change that code without asking. Together they let it run anything: it writes the command into a test or script, then runs the test. Keep one of the two in ask, or run Claude Code in its sandbox.

  12. TipBypass mode can still be switched on

    disableBypassPermissionsMode

    Setting disableBypassPermissionsMode to "disable" means nobody can start this setup with --dangerously-skip-permissions. It works in any settings file, and in managed settings nobody can undo it.

  13. TipA rule that never takes effect

    Bash(git push origin feature *) never runs on its own: Bash(git push *) asks first. Claude Code checks deny, then ask, then allow, and the first match decides, so a narrower allow never wins over a broader ask.

  14. TipAllow rules wait for folder trust

    Allow rules in a shared .claude/settings.json apply only after each person accepts the folder trust dialog, and never in a claude -p run of an untrusted folder. Ask and deny rules apply at once.

The file, fixed

Every fix makes Claude Code more careful. None of them allows anything new.

What the checker looks for

It reads the file the way Claude Code does and only calls a rule safe when the text shows it. The rule syntax follows Claude Code’s permissions documentation, checked 20 November 2026. It sees one file: Claude Code joins the lists from all of them, so check each one you use.

What the Claude Code settings checker flags
OptionFor exampleWhy it matters
Allow rules that let in everythingFor exampleBash, Bash(python *), Bash(npx *), Bash(curl *), Bash(git *)Why it mattersCommands that start other programs, reach other machines or can't be undone, allowed without a question.
Rules that never take effectFor exampleBash(git push origin feature *) under an ask of Bash(git push *)Why it mattersDeny, then ask, then allow, and the first match decides. A narrower allow never wins.
Rules Claude Code skipsFor examplebash(…), mcp__server__tool(*), Read(/Users/…), Write(./src/**)Why it mattersWrong case, brackets on MCP rules, a single slash that is not the disk's root, Write paths Claude Code never matches.
Secrets left openFor exampleNo deny on .env, SSH or cloud keysWhy it mattersWithout one, Claude Code reads them like any file and their contents can land in the conversation.
Modes and combinationsFor examplebypassPermissions, dontAsk, acceptEdits with allowed testsWhy it mattersModes that skip questions, and edit-then-run: an allowed test runs whatever Claude Code just wrote into it.
The rest of the fileFor exampleAPI keys in env, enableAllProjectMcpServers, ~ in additionalDirectoriesWhy it mattersKeys checked into git, servers a cloned repository starts unasked, the whole home folder opened up.

Keep the asks, lose the waiting

The careful file asks more often. With the VariantGate hook, each question Claude Code would ask you reaches your phone, email, Slack, Teams or Discord, and the session goes on when you answer. Free for one person and 100 requests a month, with no card.

Questions

How do I check what my Claude Code settings allow?

Paste the file into the checker above, or run /permissions inside Claude Code to see the rules in effect. Claude Code joins the allow, ask and deny lists of every settings file, so check ~/.claude/settings.json, .claude/settings.json and .claude/settings.local.json, and any managed settings your company sets.

Does Bash(npm *) also match plain npm?

Yes. A star at the end with a space before it also matches the command with no arguments, so Bash(npm *) covers npm on its own as well as npm publish. Bash(ls *) does not match lsof. The older Bash(npm:*) means the same.

Why doesn't my Read(/Users/...) deny rule work?

In Read and Edit rules a single leading slash means the folder of the settings file's project (or ~/.claude for user settings), not the root of the disk. Read(/Users/me/.ssh/**) never matches your keys. Write Read(//Users/me/.ssh/**) or Read(~/.ssh/**).

Is it safe to allow Bash(python *) or Bash(npx *)?

No. python, node, npx, bash, docker run, sudo, env and xargs start whatever comes after them, so allowing any of them allows every command. Allow the exact commands you mean, such as Bash(python -m pytest *), and leave the rest to ask.

Can a hook that answers allow get past my ask and deny rules?

No. A PreToolUse hook that returns allow does not get past a deny rule, and a matching ask rule still prompts. A PermissionRequest hook answers only the questions Claude Code would ask you, and it cannot approve what a deny rule refuses.

Does bypassPermissions in a project's settings.json still work?

Not since Claude Code 2.1.257: defaultMode bypassPermissions and auto take effect only from user or managed settings, or from --permission-mode for one session. Older versions honoured it from any file, so the checker still flags it.

Is my settings file sent anywhere?

No. The checker runs in your browser, sends nothing, and has no share link, because settings files can hold keys. It shows the names of env entries that look like secrets, never their values.