Answer: The /tools command returns an empty list or fewer tools than expected due to common causes such as an empty tools array in the custom agent configuration, typos in tool names, incorrect MCP server tool names (missing server prefix), or MCP server configuration issues preventing tool loading. Unexpected permission prompts occur for tools listed in allowedTools, so ensure tools are listed in both tools and allowedTools arrays and check for typos between the two arrays. Status: Confirmed Entry: tool/kiro/permissions-and-security/tool-permission-problems Revision: 1 Digest: sha256:ab2da3acdce76796 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:39:55Z Last changed: 2026-11-13T03:39:55Z Last verified: 2026-11-20T13:25:05Z Next check: 2026-11-21T13:25:05Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of empty list cause 1 | Empty tools array in the custom agent configuration | [1] | 2026-11-20 empty list cause 2 | Typos in tool names within the tools array | [1] | 2026-11-20 empty list cause 3 | Incorrect MCP server tool names (missing server prefix) | [1] | 2026-11-20 empty list cause 4 | MCP server configuration issues preventing tool loading | [1] | 2026-11-20 permission prompt solution | Ensure tools are listed in both tools and allowedTools arrays | [1] | 2026-11-20 permission prompt check | Check for typos in tool names between the two arrays | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Troubleshooting - Custom agents - Features - Docs - Kiro". https://kiro.dev/docs/custom-agents/troubleshooting/ Role: primary. Accessed: 2026-11-20T13:25:05Z Quote: "Empty tools array in the custom agent configuration" (Supports: empty list cause 1) Quote: "Typos in tool names within the tools array" (Supports: empty list cause 2) Quote: "Incorrect MCP server tool names (missing server prefix)" (Supports: empty list cause 3) Quote: "MCP server configuration issues preventing tool loading" (Supports: empty list cause 4) Quote: "Ensure tools are listed in both tools and allowedTools arrays" (Supports: permission prompt solution) Quote: "Check for typos in tool names between the two arrays" (Supports: permission prompt check) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 0a96825622ee1af1cfe19ea51440f391320678a8f2aa26be1a6419b712c07955 (captured 2026-11-20T13:25:03Z) 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:25:05Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:25:05Z Last attempt: 2026-11-20T13:25:05Z Notes and limitations: Extracted automatically from a single official source (section "Tool permission problems"). Related: 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/kiro/permissions-and-security/trusted-commands How do I configure trusted commands in Kiro? https://latestn.com/tool/kiro/permissions-and-security/support-power-iam-permissions What IAM permissions are required to use the Kiro Support power? 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/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:39:55Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/permissions-and-security/tool-permission-problems/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-permission-problems POST: https://latestn.com/dispute/tool/kiro/permissions-and-security/tool-permission-problems with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/permissions-and-security/tool-permission-problems?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). Why does the /tools command return an empty list or show unexpected permission prompts in Kiro? Revision 1, last verified 2026-11-20T13:25:05Z. https://latestn.com/tool/kiro/permissions-and-security/tool-permission-problems (accessed 2026-11-21T10:03:58Z). @misc{LatestN_tool_kiro_permissions_and_security_tool_permission_problems_r1, title = {Why does the /tools command return an empty list or show unexpected permission prompts in Kiro?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/permissions-and-security/tool-permission-problems}}, note = {Revision 1; digest sha256:ab2da3acdce76796; last verified 2026-11-20T13:25:05Z; accessed 2026-11-21T10:03:58Z} } 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-permission-problems