{"version":"2.1.269","anchor":"eval-mocks-now-interact-with-managed-mcp-policy-enterprise","canonical_anchor":"eval-mocks-now-interact-with-managed-mcp-policy-enterprise","heading":"Eval mocks now interact with managed MCP policy (enterprise) explicitly","tier":"internal","area":"Plugin Eval","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/eval-mocks-now-interact-with-managed-mcp-policy-enterprise","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Eval mocks now interact with managed MCP policy (enterprise) explicitly\n\nEval mocks now explicitly check managed MCP server policy before starting\n\n**What**\n\nClaude 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:\n\n- `MockWithholdPolicyError`: thrown when an organization's `allowedMcpServers`\/`deniedMcpServers` policy would block the empty withholding stand-in from starting\n\n- `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\n\n**Why**\n\nThis makes eval failures caused by enterprise MCP policy restrictions clearer and easier to diagnose, instead of failing in a generic or confusing way.\n\n- Area: Plugin Eval\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}