Follow Discord
Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.269 ·

Eval mocks now interact with managed MCP policy (enterprise) explicitly

← All of v2.1.269 Home All releases

Eval mocks now explicitly check managed MCP server policy before starting

TierUnder the hoodhow much it should matter to you
Useful1my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaPlugin Evalwhat it touches
KindInternal Changesin v2.1.269,
Under the hood

Eval mocks now explicitly check managed MCP server policy before starting

What

Claude Code's internal evaluation harness (the "eval" system used for testing) now has two specific errors for when a mock MCP server (a stand-in for a real MCP server, used in testing) can't be started:

  • MockWithholdPolicyError: thrown when an organization's allowedMcpServers/deniedMcpServers policy would block the empty withholding stand-in from starting
  • MockEnterpriseExclusiveError: thrown when a machine's managed-mcp.json file gives the organization exclusive control over MCP servers, meaning eval mocks can't run on that machine at all
Why

This makes eval failures caused by enterprise MCP policy restrictions clearer and easier to diagnose, instead of failing in a generic or confusing way.

See this entry in the whole of v2.1.269 →