{"version":"2.1.269","anchor":"agent-mock-plugin-eval-results-can-now-report-a-withheld-s","canonical_anchor":"agent-mock-plugin-eval-results-can-now-report-a-withheld-s","heading":"Agent-mock plugin eval results can now report a 'withheld' server","tier":"internal","area":"Plugin Eval","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/agent-mock-plugin-eval-results-can-now-report-a-withheld-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Agent-mock plugin eval results can now report a 'withheld' server\n\nPlugin eval mock runs can now flag an MCP server as 'withheld' in results\n\n**Unclear.** What causes a server to be marked withheld, and what practical effect it has on the eval, isn't stated.\n\n**What**\n\nWhen running a mock evaluation of a plugin, the summary of results for each MCP server can now include a `withheld: true` flag, in addition to the existing `replayPinned` count.\n\n**Why**\n\nThis lets plugin developers see when a server was withheld during a mock eval run, giving clearer insight into what happened during testing.\n\n- Area: Plugin Eval\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}