Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.304 ·

Hooks that call MCP tools can be refused by the server's settings

An mcp_tool hook can now be refused because of its MCP server's configuration, and hook matching treats Claude Code's own MCP tools like built-in ones

You'll notice Improvements
JSON All of v2.1.304
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
HooksArea: what it touches
ImprovementsKind: in v2.1.304,
ImprovementsSection of the release

Unclear It is not clear which server settings cause an mcp_tool hook to be refused.

What

An mcp_tool hook is a hook (an action set to run automatically at certain points) that calls a tool on an MCP server. Claude Code used to refuse such a hook only for the account memory server. It now also checks any server's configuration for a refusal, both before and after connecting to it. A refused call is reported as withheld.

Hook matchers, the patterns that decide which tools a hook applies to, now treat MCP tools that belong to Claude Code itself the same way as built-in tools, including matching them by their group name. If the same hook would be triggered twice through that group routing, it now runs only once.

Why

This changes which hooks fire for MCP tools, so a hook that targets one of these tools may now run, run once instead of twice, or be refused.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear which server settings cause an `mcp_tool` hook to be refused.

See this entry in the whole of v2.1.304 →

Feedback