{"version":"2.1.257","anchor":"mcp-managed-policy-blocking-now-carries-a-specific-reason-in","canonical_anchor":"mcp-managed-policy-blocking-now-carries-a-specific-reason-in","heading":"MCP managed-policy blocking now carries a specific reason instead of a generic error","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/mcp-managed-policy-blocking-now-carries-a-specific-reason-in","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### MCP managed-policy blocking now carries a specific reason instead of a generic error\n\nA server blocked by managed policy now records why, such as policy mismatch or scope not allowed, instead of one error.\n\nWhen an MCP server is blocked or disabled by managed policy, the failed-client state now carries a specific block reason instead of one generic error, distinguishing cases like policy-mismatch vs. scope-not-allowed vs. other managed-policy reasons so the UI and telemetry can show why a server was blocked.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}