Answer: The text describes a tool approval process where you review each tool request carefully before approval, checking the parameters being passed and understanding what the tool will do before approving it, and denying any suspicious requests that don't match your current task. The text does not mention auto-approval or when to use it. Status: Confirmed Entry: tool/kiro/permissions-and-security/mcp-tool-approval Revision: 1 Digest: sha256:f00928b3f8384366 (changes whenever the content changes) Timeline: Created: 2026-11-14T13:28:07Z Last changed: 2026-11-14T13:28:07Z Last verified: 2026-11-20T13:30:32Z Next check: 2026-11-21T13:30:32Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of approval step | Review each tool request carefully before approval | [1] | 2026-11-20 parameter check | Check the parameters being passed to the tool | [1] | 2026-11-20 understanding action | Understand what the tool will do before approving it | [1] | 2026-11-20 denial guidance | Deny any suspicious requests that don't match your current task | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Best practices - MCP - Features - Docs - Kiro". https://kiro.dev/docs/mcp/security/ Role: primary. Accessed: 2026-11-20T13:30:32Z Quote: "Review each tool request carefully before approval" (Supports: approval step) Quote: "Check the parameters being passed to the tool" (Supports: parameter check) Quote: "Understand what the tool will do before approving it" (Supports: understanding action) Quote: "Deny any suspicious requests that don't match your current task" (Supports: denial guidance) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: d4b30fc046d7791e35e13611dcd8e357218fdb5d530e144fdb7ded44b3acaa6f (captured 2026-11-20T13:30:33Z) 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:30:32Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:30:32Z Last attempt: 2026-11-20T13:30:32Z Notes and limitations: Extracted automatically from a single official source (section "Tool approval process"). Related: https://latestn.com/tool/kiro/permissions-and-security/migrate-acp-permissions-consent How do I migrate permissions and consent when moving a Kiro ACP client to CLI V3? https://latestn.com/tool/kiro/permissions-and-security/migrate-permissions-from-0x How do I migrate my Kiro permissions from 0.x to 1.0? https://latestn.com/tool/kiro/permissions-and-security/mobile-app-lock How do I enable or disable app lock in the Kiro mobile app? https://latestn.com/tool/kiro/permissions-and-security/kgl-web-access-domain-block How do I set up a Kiro KGL policy that asks before web access and blocks a specific domain? https://latestn.com/tool/kiro/permissions-and-security/limit-hook-scope How do I limit the scope of Kiro hooks? https://latestn.com/tool/kiro/permissions-and-security/mcp-environment-variables How do I use environment variables for MCP server configuration in Kiro? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-14T13:28:07Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/permissions-and-security/mcp-tool-approval/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/mcp-tool-approval POST: https://latestn.com/dispute/tool/kiro/permissions-and-security/mcp-tool-approval with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/permissions-and-security/mcp-tool-approval?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How does the MCP tool approval process work in Kiro and when should I use auto-approval? Revision 1, last verified 2026-11-20T13:30:32Z. https://latestn.com/tool/kiro/permissions-and-security/mcp-tool-approval (accessed 2026-11-21T10:08:01Z). @misc{LatestN_tool_kiro_permissions_and_security_mcp_tool_approval_r1, title = {How does the MCP tool approval process work in Kiro and when should I use auto-approval?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/permissions-and-security/mcp-tool-approval}}, note = {Revision 1; digest sha256:f00928b3f8384366; last verified 2026-11-20T13:30:32Z; accessed 2026-11-21T10:08:01Z} } 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/mcp-tool-approval