Skip to content
AgentAtlas

Kiro Permissions: permissions.yaml Allow, Ask and Deny Rules

How do I let Kiro run commands or edit files without asking?

Create ~/.kiro/settings/permissions.yaml with rules that set a capability, optional match patterns and an effect of allow, ask or deny. Deny always wins over ask, and ask wins over allow, across every scope. Workspace rules live outside the repo in ~/.kiro/workspace-roots/<hash>/permissions.yaml.

Compare: allow all commands in every AI coding agent →

Capabilities and effects

  • Capabilities: fs_read, fs_write, shell, web_fetch, web_search, mcp, subagent, skill, power, context, diagnostics, sandbox_network.
  • Meta-capabilities: all, builtin, filesystem.
  • Effects: deny (always block), ask (prompt you), allow (proceed silently).

Pre-approve trusted actions

~/.kiro/settings/permissions.yaml

rules:
  - capability: shell
    match: ["git *", "npm *", "npx *"]
    effect: allow

  - capability: fs_write
    match: ["src/**", "tests/**"]
    effect: allow

  - capability: fs_read
    effect: allow

  - capability: mcp
    match: ["my-server/*"]
    effect: allow

Allow everything except some commands

permissions.yaml

rules:
  - capability: shell
    effect: allow
    match:
      - "npm *"
    exclude:
      - "npm publish*"

  - capability: fs_read
    effect: deny
    match:
      - "**/.env"
      - "**/.env.*"
      - "secrets/**"
      - "**/*.pem"

Compound shell commands joined with ;, &&, || or | are split, and each part is checked on its own.

Pattern rules

  • File patterns: * matches within one path part, ** matches across folders. Brace expansion and [abc] classes work.
  • Shell, web and MCP patterns: * matches any characters. **, ? and character classes are not supported.

Default behavior

Without a permissions.yaml, Kiro allows reading workspace files, common read-only git commands and system info commands. Everything else asks. Writes to .kiro/settings/ and ~/.kiro/settings/ are always denied. Writes to .git/**, .vscode/** and the .kiro agents, hooks, workflows and powers folders always ask. You cannot change these hardcoded rules.

In headless runs with no interactive client, every ask is treated as deny, so only allowed actions run.

Sources

More Kiro guides

Reviewed Oct 23, 2026. Settings change often; the linked vendor docs are the source of truth.

Built an MCP server? Get it listed everywhere →

Shipping an Android app? Google Play needs 12 testers for 14 days first. Get them with Tester Exchange →