Answer: For MCP tools, V3 Hook events use the sanitized internal tool ID mcp__ rather than the @server/tool display name, and this applies to Pre Tool Use, Permission Request, and Post Tool Use Hooks when targeting MCP server tools. In the Hook's matcher, use either the @ or @/ selector or a regex against the internal ID. Status: Confirmed Entry: tool/kiro/integrations/mcp-tool-hooks Revision: 3 Digest: sha256:f3c5925a9a614a40 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:42:11Z Last changed: 2026-11-19T13:20:22Z (Tool ID format: — → mcp__) Last verified: 2026-11-20T13:28:41Z Next check: 2026-11-21T13:28:41Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Tool ID format | mcp__ | [1] | 2026-11-20 Example tool_name | mcp_postgres_query | [1] | 2026-11-20 Applicable hook types | Pre Tool Use, Permission Request, and Post Tool Use Hooks | [1] | 2026-11-20 Matcher selectors | @ or @/ | [1] | 2026-11-20 Page updated | November 18, 2026 | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Hook triggers - Hooks - Features - Docs - Kiro". https://kiro.dev/docs/hooks/types/ Role: primary. Accessed: 2026-11-20T13:28:41Z Quote: "V3 Hook events use the sanitized internal tool ID mcp__" (Supports: Tool ID format) Quote: ""tool_name" : "mcp_postgres_query"" (Supports: Example tool_name) Quote: "This applies to Pre Tool Use, Permission Request, and Post Tool Use Hooks when targeting MCP server tools." (Supports: Applicable hook types) Quote: "use either the @ or @/ selector or a regex against the internal ID" (Supports: Matcher selectors) Quote: "Page updated: November 18, 2026" (Supports: Page updated) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: ca71d565da91daa04e6aebab87f05edf52a7429e6798d193ff2eb61ab5a678fc (captured 2026-11-20T13:28:40Z) 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:28:41Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:28:41Z Last attempt: 2026-11-20T13:28:41Z Notes and limitations: Extracted automatically from a single official source (section "MCP tool hooks"). Related: https://latestn.com/tool/kiro/integrations/mix-gitlab-github Can I use GitLab and GitHub together in one Kiro session? https://latestn.com/tool/kiro/integrations/mobile-git-providers How do I connect a Git provider in the Kiro mobile app? https://latestn.com/tool/kiro/integrations/open-pull-request How do I open a pull request from a Kiro web agent session? https://latestn.com/tool/kiro/integrations/mcp-server-config How do I configure an MCP server in Kiro's agent config? https://latestn.com/tool/kiro/integrations/mcp-servers-multi-root How are MCP servers configured in Kiro multi-root workspaces? https://latestn.com/tool/kiro/integrations/mcp-servers-not-in-registry How do I use an MCP server in Kiro that isn't in the registry? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-19T13:20:22Z | changed | Tool ID format: — → mcp__ | [1] 2026-11-19T13:20:22Z | changed | Page updated: November 17, 2026 → November 18, 2026 | [1] 2026-11-19T13:20:22Z | changed | Internal tool ID format: mcp__ → — | [1] 2026-11-17T13:51:12Z | changed | Internal tool ID format: — → mcp__ | [1] 2026-11-17T13:51:12Z | changed | Page updated: November 12, 2026 → November 17, 2026 | [1] 2026-11-17T13:51:12Z | changed | Applicable hook types: Pre Tool Use and Post Tool Use → Pre Tool Use, Permission Request, and Post Tool Use Hooks | [1] 2026-11-17T13:51:12Z | changed | Tool ID format: mcp__ → — | [1] 2026-11-13T03:42:11Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/integrations/mcp-tool-hooks/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/integrations/mcp-tool-hooks POST: https://latestn.com/dispute/tool/kiro/integrations/mcp-tool-hooks with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/integrations/mcp-tool-hooks?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I use MCP tool hooks in Kiro? Revision 3, last verified 2026-11-20T13:28:41Z. https://latestn.com/tool/kiro/integrations/mcp-tool-hooks (accessed 2026-11-21T09:57:15Z). @misc{LatestN_tool_kiro_integrations_mcp_tool_hooks_r3, title = {How do I use MCP tool hooks in Kiro?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/integrations/mcp-tool-hooks}}, note = {Revision 3; digest sha256:f3c5925a9a614a40; last verified 2026-11-20T13:28:41Z; accessed 2026-11-21T09:57:15Z} } 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/integrations/mcp-tool-hooks