When 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.
MCP managed-policy blocking now carries a specific reason instead of a generic error
A server blocked by managed policy now records why, such as policy mismatch or scope not allowed, instead of one error.
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
MCPArea: what it touches
ImprovementsKind: in v2.1.257,
ImprovementsSection of the release