Answer: Per-tool permissions are configured in the agent config under toolsSettings, where each tool (such as shell or read) has its own allowed and denied patterns. For example, shell uses allowedCommands and deniedCommands regex patterns, while read uses allowedPaths and deniedPaths gitignore-style glob patterns. Status: Confirmed Entry: tool/kiro/permissions-and-security/cli-tools-settings-permissions Revision: 1 Digest: sha256:82a4f07c32481efc (changes whenever the content changes) Timeline: Created: 2026-11-13T03:36:02Z Last changed: 2026-11-13T03:36:02Z Last verified: 2026-11-20T13:19:09Z Next check: 2026-11-21T13:19:09Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of config key | toolsSettings | [1] | 2026-11-20 shell allowed commands | allowedCommands | [1] | 2026-11-20 shell denied commands | deniedCommands | [1] | 2026-11-20 read allowed paths | allowedPaths | [1] | 2026-11-20 read denied paths | deniedPaths | [1] | 2026-11-20 allowedCommands description | Regex patterns for auto-approved shell commands | [1] | 2026-11-20 deniedCommands description | Regex patterns for blocked shell commands | [1] | 2026-11-20 allowedPaths description | Gitignore-style glob patterns for auto-approved file paths | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "2.x reference - CLI - Docs - Kiro". https://kiro.dev/docs/cli/2x-reference/ Role: primary. Accessed: 2026-11-20T13:19:09Z Quote: "Per-tool settings in agent config ( toolsSettings )" (Supports: config key) Quote: ""allowedCommands" : [ "git *" , "npm *" ]" (Supports: shell allowed commands) Quote: ""deniedCommands" : [ "rm -rf *" , "sudo *" ]" (Supports: shell denied commands) Quote: ""allowedPaths" : [ "src/**" ]" (Supports: read allowed paths) Quote: ""deniedPaths" : [ "*.env" ]" (Supports: read denied paths) Quote: "Regex patterns for auto-approved shell commands" (Supports: allowedCommands description) Quote: "Regex patterns for blocked shell commands" (Supports: deniedCommands description) Quote: "Gitignore-style glob patterns for auto-approved file paths" (Supports: allowedPaths description) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: ab3c2fd4f3930e9d5bc77abf8828704b7d82aeed870a07c64709dc423f6a9548 (captured 2026-11-20T13:19:09Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T13:19:09Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:19:09Z Last attempt: 2026-11-20T13:19:09Z Notes and limitations: Extracted automatically from a single official source (section "Per-tool settings in agent config ( toolsSettings )"). Related: https://latestn.com/tool/kiro/permissions-and-security/cloud-session-safety Is it safe to let a Kiro cloud session run autonomously? https://latestn.com/tool/kiro/permissions-and-security/configure-bot-permissions How do I configure permissions for a Kiro Crew bot? https://latestn.com/tool/kiro/permissions-and-security/configure-iam-role-sandbox How do I configure an IAM role for the Kiro sandbox? https://latestn.com/tool/kiro/permissions-and-security/capability-based-permissions-how-it-works How do capability-based permissions work in Kiro 1.0? https://latestn.com/tool/kiro/permissions-and-security/ci-headless-permissions How do I configure Kiro CLI permissions for CI or headless environments? https://latestn.com/tool/kiro/permissions-and-security/cli-permissions-flags-commands What CLI flags and slash commands does Kiro CLI 2.x provide for permissions and tool trust? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:36:02Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/permissions-and-security/cli-tools-settings-permissions/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/kiro/permissions-and-security/cli-tools-settings-permissions POST: https://latestn.com/dispute/tool/kiro/permissions-and-security/cli-tools-settings-permissions with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/permissions-and-security/cli-tools-settings-permissions?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I configure per-tool permissions in the Kiro CLI agent config? Revision 1, last verified 2026-11-20T13:19:09Z. https://latestn.com/tool/kiro/permissions-and-security/cli-tools-settings-permissions (accessed 2026-11-21T10:03:35Z). @misc{LatestN_tool_kiro_permissions_and_security_cli_tools_settings_permissions_r1, title = {How do I configure per-tool permissions in the Kiro CLI agent config?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/permissions-and-security/cli-tools-settings-permissions}}, note = {Revision 1; digest sha256:82a4f07c32481efc; last verified 2026-11-20T13:19:09Z; accessed 2026-11-21T10:03:35Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/kiro/permissions-and-security/cli-tools-settings-permissions