Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.269 ·

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

Eval mocks now explicitly check managed MCP server policy before starting

Under the hood Internal Changes
JSON All of v2.1.269
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Plugin EvalArea: what it touches
Internal ChangesKind: in v2.1.269,
Internal ChangesSection of the release
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 →

Feedback