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.299 ·

MCP allow rules no longer approve tools from a different MCP server

MCP allow rules are matched more strictly, and Claude Code warns when one cannot approve a tool from another MCP server

You'll notice Bug Fixes
JSON All of v2.1.299
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PermissionsArea: what it touches
Bug FixesKind: in v2.1.299,
Bug FixesSection of the release

Unclear It is not clear whether an allow rule that matched before this change will now prompt instead.

What

Permission rules decide which tools Claude Code may run without asking you. They can allow a tool, deny it, or ask about it. Claude Code has changed how these rules are matched against MCP tools, which are tools supplied by outside programs called MCP servers.

  • Allow rules: now only match when the rule covers the tool's own MCP server, and the rule name must also match the tool.
  • Deny and ask rules: also match when the rule names the MCP server.

When an allow rule does not cover a tool that belongs to another MCP server, Claude Code logs a warning, once for each tool name. The warning suggests writing the rule as server* or using the tool's full name.

Why

Tools that used to run without a prompt may now ask for permission. If you see that warning, rewrite the rule in the server* form or name the tool in full.

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 whether an allow rule that matched before this change will now prompt instead.

See this entry in the whole of v2.1.299 →

Feedback