Answer: You can create your own trusted commands list by searching for Kiro Agent: Trusted Commands in your settings. Kiro uses simple string prefix matching, with exact matching, wildcard matching using *, and universal trust using * alone. Status: Confirmed Entry: tool/kiro/permissions-and-security/trusted-commands Revision: 2 Digest: sha256:53f9e619866fd1f1 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:44:12Z Last changed: 2026-11-20T13:31:31Z (Universal trust: — → *) Last verified: 2026-11-20T13:31:31Z Next check: 2026-11-21T13:31:31Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Setting to search | Kiro Agent: Trusted Commands | [1] | 2026-11-20 Matching method | simple string prefix matching | [1] | 2026-11-20 Exact matching example | npm install | [1] | 2026-11-20 Wildcard matching example | npm * | [1] | 2026-11-20 Universal trust | * | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Privacy and Security - Docs - Kiro". https://kiro.dev/docs/privacy-and-security/ Role: primary. Accessed: 2026-11-20T13:31:31Z Quote: "searching for Kiro Agent: Trusted Commands in your settings" (Supports: Setting to search) Quote: "Kiro uses simple string prefix matching to determine if a command should be automatically trusted" (Supports: Matching method) Quote: "Exact matching : Commands must match exactly (e.g., npm install )" (Supports: Exact matching example) Quote: "Wildcard matching : Use * to trust command variations (e.g., npm * trusts all npm commands)" (Supports: Wildcard matching example) Quote: "Universal trust : Use * alone to trust all commands (use with extreme caution)" (Supports: Universal trust) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 2a27777037863f292c7fdc481c16399c726b0099bc5e7d7c1945f8ad94e5abf8 (captured 2026-11-20T13:31:31Z) 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:31Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:31:31Z Last attempt: 2026-11-20T13:31:31Z Notes and limitations: Extracted automatically from a single official source (section "Trusted commands"). Related: 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/validate-hook-inputs How do I validate inputs in Kiro hooks for security? https://latestn.com/tool/kiro/permissions-and-security/vpc-iam-roles What IAM roles does Kiro need to connect cloud sessions to a VPC? 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/kiro/permissions-and-security/tool-permissions How do I set tool permissions for Kiro's built-in tools? https://latestn.com/tool/kiro/permissions-and-security/trust-workspace-cli How do I trust a workspace in Kiro CLI? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:31:31Z | changed | Universal trust: — → * | [1] 2026-11-20T13:31:31Z | changed | Wildcard matching example: — → npm * | [1] 2026-11-20T13:31:31Z | changed | Exact matching example: — → npm install | [1] 2026-11-20T13:31:31Z | changed | Matching method: — → simple string prefix matching | [1] 2026-11-20T13:31:31Z | changed | Setting to search: — → Kiro Agent: Trusted Commands | [1] 2026-11-20T13:31:31Z | changed | universal trust: * → — | [1] 2026-11-20T13:31:31Z | changed | wildcard matching: * → — | [1] 2026-11-20T13:31:31Z | changed | default behavior: requires approval before running any command → — | [1] 2026-11-20T13:31:31Z | changed | setting to search: Kiro Agent: Trusted Commands → — | [1] 2026-11-13T03:44:12Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/permissions-and-security/trusted-commands/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/trusted-commands POST: https://latestn.com/dispute/tool/kiro/permissions-and-security/trusted-commands with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/permissions-and-security/trusted-commands?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I configure trusted commands in Kiro? Revision 2, last verified 2026-11-20T13:31:31Z. https://latestn.com/tool/kiro/permissions-and-security/trusted-commands (accessed 2026-11-21T10:06:24Z). @misc{LatestN_tool_kiro_permissions_and_security_trusted_commands_r2, title = {How do I configure trusted commands in Kiro?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/permissions-and-security/trusted-commands}}, note = {Revision 2; digest sha256:53f9e619866fd1f1; last verified 2026-11-20T13:31:31Z; accessed 2026-11-21T10:06:24Z} } 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/trusted-commands