{"version":"2.1.309","anchor":"hooks-of-type-mcp-tool-refused-for-the-artifacts-mcp-server","canonical_anchor":"hooks-of-type-mcp-tool-refused-for-the-artifacts-mcp-server","heading":"Hooks can no longer call the Artifacts server or the cloud browser","tier":"notice","area":"Hooks","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/hooks-of-type-mcp-tool-refused-for-the-artifacts-mcp-server","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Hooks can no longer call the Artifacts server or the cloud browser\n\nAn `mcp_tool` hook aimed at the Artifacts MCP server or the session's cloud browser is now refused, and permission hooks cannot approve cloud browser calls\n\n**Unclear.** It is not clear exactly which setups of the Artifacts server are covered by the refusal.\n\n**What**\n\nA hook is an action you set up to run automatically at certain points while Claude Code works. An `mcp_tool` hook calls a tool on an MCP server, which is an outside program that gives Claude Code extra tools. Claude Code already refused some of these hooks. It now also refuses an `mcp_tool` hook when it targets:\n\n- the Artifacts MCP server\n\n- the cloud browser in a cloud session, which is a web browser that runs in the cloud\n\nThe cloud browser rule only applies in sessions that have one. When it refuses a hook, Claude Code tells you to remove the hook or point it at another server.\n\nA `PermissionRequest` hook runs when a tool call needs a permission decision. It now cannot approve a call to the cloud browser's tools or loosen the rules for them.\n\n**Why**\n\nA hook's tool call skips auto mode's safety check and your approval. Blocking it for these servers stops that shortcut. If you have hooks pointing at either one, they will stop working.\n\n- Area: Hooks\n- Names: `mcp_tool`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}