Next step

More settings in permissions, in alphabetical order.

• Setting · permissions Deny Sensitive Files Deny access to sensitive files like environment variables and secrets.
  npx … --setting permissions/deny-sensitive-files

  Add to stack
• Setting · permissions Development Mode Comprehensive permissions for active development. Allows most development tools and operations while maintaining security boundaries. Ideal for trusted development environments where productivity is prioritized.
  npx … --setting permissions/development-mode

  Add to stack
• Setting · permissions Mintlify MCP Confirm Writes Ask before Claude runs a Mintlify admin MCP tool that publishes, merges, deletes or has site-wide effect: publish (which can also merge the pull request), discard, delete_node, move_node (renames page paths), update_config (theme, redirects, SEO, integrations), approving or publishing review requests, and every project-management write (deployment settings, custom domain, Git source, authentication, automations and their pull requests, members). Page edits, comments and reads still run freely: they stay unpublished until publish, except in projects with auto publish and in bases, where Mintlify commits them to the deploy branch at once (add ask rules for edit_page and write_page there). Ask rules win over allow rules, so this holds even if mcp__mintlify-admin is allowed. Only covers a server named 'mintlify-admin' (as installed by --mcp devtools/mintlify-admin).
  npx … --setting permissions/mintlify-mcp-confirm-writes

  Add to stack
• Setting · permissions Read Only Mode Restrict Claude to read-only operations for code review and analysis. Prevents any file modifications or command executions, making it safe for exploring unfamiliar codebases or conducting security audits.
  npx … --setting permissions/read-only-mode

  Add to stack
• Setting · permissions Stripe MCP Confirm Writes Ask before Claude runs a Stripe MCP tool that writes data, moves money or starts a Stripe Atlas company formation; read and docs tools still run freely. Stripe's MCP docs recommend client-side tool approval, since Stripe itself only confirms some writes (refunds, outbound payments). Only covers a server named 'stripe' (as installed by --mcp devtools/stripe); under any other name nothing is prompted.
  npx … --setting permissions/stripe-mcp-confirm-writes

  Add to stack
• Setting · permissions Additional Directories Grant access to additional directories outside the current project. Useful for monorepo setups, shared libraries, or when working with documentation stored in separate repositories.
  npx … --setting permissions/additional-directories

  Add to stack