Answer: You restrict which tools a Kiro custom agent can use with the allowedTools field, which accepts exact matches, server-level permissions, and glob-style wildcard patterns using * and ?. Note that allowedTools belongs to CLI 2.x, and unlike the tools field it does not support the "*" wildcard for allowing all tools. Status: Confirmed Entry: tool/kiro/permissions-and-security/custom-agent-allowed-tools Revision: 2 Digest: sha256:05db6d144f531fb0 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:39:46Z Last changed: 2026-11-20T13:24:50Z (unsupported wildcard: — → *) Last verified: 2026-11-20T13:24:50Z Next check: 2026-11-21T13:24:50Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of field name | allowedTools | [1] | 2026-11-20 wildcard characters | * and ? | [1] | 2026-11-20 exact match example | @git/git_status | [1] | 2026-11-20 server-level example | @fetch | [1] | 2026-11-20 builtin prefix | @builtin | [1] | 2026-11-20 unsupported wildcard | * | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Configuration reference - Custom agents - Features - Docs - Kiro". https://kiro.dev/docs/custom-agents/configuration-reference/ Role: primary. Accessed: 2026-11-20T13:24:50Z Quote: "The allowedTools field belongs to CLI 2.x." (Supports: field name) Quote: "supports glob-style wildcard patterns using * and ?" (Supports: wildcard characters) Quote: "Specific MCP tools : "@server_name/tool_name" (e.g., "@git/git_status" )" (Supports: exact match example) Quote: "All tools from MCP server : "@server_name" (e.g., "@fetch" )" (Supports: server-level example) Quote: "Optionally, you can also prefix native tools with the namespace @builtin ." (Supports: builtin prefix) Quote: "the allowedTools field does not support the "*" wildcard for allowing all tools." (Supports: unsupported wildcard) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: ecce5c93570c3b9c85e0b2a1731b601324e575e0637fef02f4e88318615a0e85 (captured 2026-11-20T13:24:48Z) 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:24:50Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:24:50Z Last attempt: 2026-11-20T13:24:50Z Notes and limitations: Extracted automatically from a single official source (section "AllowedTools field"). Related: https://latestn.com/tool/kiro/permissions-and-security/define-permission-rules How do I define permission rules in Kiro? https://latestn.com/tool/kiro/permissions-and-security/delegate-agent-approval How does the agent approval flow work in Kiro CLI delegate? https://latestn.com/tool/kiro/permissions-and-security/discord-allowlist How does the deny-by-default allowlist work for Kiro Crew on Discord? 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/configure-tool-access How do I configure which built-in tools Kiro can access? https://latestn.com/tool/kiro/permissions-and-security/create-trust-policy-iam-role How do I create a trust policy for an IAM role in Kiro? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:24:50Z | changed | unsupported wildcard: — → * | [1] 2026-11-20T13:24:50Z | changed | builtin prefix: — → @builtin | [1] 2026-11-20T13:24:50Z | changed | server-level example: — → @fetch | [1] 2026-11-20T13:24:50Z | changed | no allow-all wildcard: * → — | [1] 2026-11-20T13:24:50Z | changed | server-level permission example: @server_name → — | [1] 2026-11-20T13:24:50Z | changed | exact match example: @server_name/tool_name → @git/git_status | [1] 2026-11-20T13:24:50Z | changed | V3 replacement: permissions.rules → — | [1] 2026-11-13T03:39:46Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/permissions-and-security/custom-agent-allowed-tools/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/custom-agent-allowed-tools POST: https://latestn.com/dispute/tool/kiro/permissions-and-security/custom-agent-allowed-tools with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/permissions-and-security/custom-agent-allowed-tools?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I restrict which tools a Kiro custom agent can use? Revision 2, last verified 2026-11-20T13:24:50Z. https://latestn.com/tool/kiro/permissions-and-security/custom-agent-allowed-tools (accessed 2026-11-21T10:03:50Z). @misc{LatestN_tool_kiro_permissions_and_security_custom_agent_allowed_tools_r2, title = {How do I restrict which tools a Kiro custom agent can use?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/permissions-and-security/custom-agent-allowed-tools}}, note = {Revision 2; digest sha256:05db6d144f531fb0; last verified 2026-11-20T13:24:50Z; accessed 2026-11-21T10:03:50Z} } 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/custom-agent-allowed-tools