Answer: Tools can be explicitly allowed in the allowedTools section of the agent configuration, for example: { "allowedTools" : [ "read" , "knowledge" , "@git/git_status" ] }. If a tool is not in the allowedTools list, the user will be prompted for permission when the tool is used unless an allowed toolsSettings configuration is set. Status: Confirmed Entry: tool/kiro/permissions-and-security/tool-permissions Revision: 2 Digest: sha256:3cb3364a98608cd4 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:44:27Z Last changed: 2026-11-20T13:31:50Z (Prompt for permission by default: — → shell , write , and aws) Last verified: 2026-11-20T13:31:50Z Next check: 2026-11-21T13:31:50Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Configuration section | allowedTools | [1] | 2026-11-20 Example configuration | { "allowedTools" : [ "read" , "knowledge" , "@git/git_status" ] } | [1] | 2026-11-20 Default trusted tools | report | [1] | 2026-11-20 Trusted in working directory | read , grep , and glob | [1] | 2026-11-20 Prompt for permission by default | shell , write , and aws | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Built-in tools - Commands and Reference - Docs - Kiro". https://kiro.dev/docs/reference/built-in-tools/ Role: primary. Accessed: 2026-11-20T13:31:50Z Quote: "Tools can be explicitly allowed in the allowedTools section of the agent configuration" (Supports: Configuration section) Quote: "{ "allowedTools" : [ "read" , "knowledge" , "@git/git_status" ] }" (Supports: Example configuration) Quote: "report is trusted by default" (Supports: Default trusted tools) Quote: "read , grep , and glob are trusted in the current working directory" (Supports: Trusted in working directory) Quote: "shell , write , and aws prompt for permission by default, but can be configured to allow specific commands/paths/services" (Supports: Prompt for permission by default) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 31ee909a7cbf48321204eabf801bb32902210e465587b7120948dabeeaf617e6 (captured 2026-11-20T13:31:49Z) 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:31:50Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:31:50Z Last attempt: 2026-11-20T13:31:50Z Notes and limitations: Extracted automatically from a single official source (section "Tool permissions"). Related: https://latestn.com/tool/kiro/permissions-and-security/trust-workspace-cli How do I trust a workspace in Kiro CLI? https://latestn.com/tool/kiro/permissions-and-security/trusted-commands How do I configure trusted commands in Kiro? https://latestn.com/tool/kiro/permissions-and-security/trusted-commands-denylist How do I configure trusted commands and the command denylist in Kiro 0.x? https://latestn.com/tool/kiro/permissions-and-security/terminal-command-approval-security How do I approve or manage command approval and security for terminal commands in Kiro? https://latestn.com/tool/kiro/permissions-and-security/tool-approval How do I approve or deny tool calls in Kiro Crew, including bulk approval and per-call reject? https://latestn.com/tool/kiro/permissions-and-security/tool-permission-problems Why does the /tools command return an empty list or show unexpected permission prompts in Kiro? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:31:50Z | changed | Prompt for permission by default: — → shell , write , and aws | [1] 2026-11-20T13:31:50Z | changed | Example configuration: — → { "allowedTools" : [ "read" , "knowledge" , "@git/git_status" ] } | [1] 2026-11-20T13:31:50Z | changed | Prompt by default: shell , write , and aws → — | [1] 2026-11-20T13:31:50Z | changed | Example allowed tools: read → — | [1] 2026-11-13T03:44:27Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/permissions-and-security/tool-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/tool-permissions POST: https://latestn.com/dispute/tool/kiro/permissions-and-security/tool-permissions with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/permissions-and-security/tool-permissions?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I set tool permissions for Kiro's built-in tools? Revision 2, last verified 2026-11-20T13:31:50Z. https://latestn.com/tool/kiro/permissions-and-security/tool-permissions (accessed 2026-11-21T10:06:12Z). @misc{LatestN_tool_kiro_permissions_and_security_tool_permissions_r2, title = {How do I set tool permissions for Kiro's built-in tools?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/permissions-and-security/tool-permissions}}, note = {Revision 2; digest sha256:3cb3364a98608cd4; last verified 2026-11-20T13:31:50Z; accessed 2026-11-21T10:06:12Z} } 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/tool-permissions