{"version":"2.1.257","anchor":"mcp-control-channel-operations-gate-on-control-channel-safe","canonical_anchor":"mcp-control-channel-operations-gate-on-control-channel-safe","heading":"MCP control-channel operations gate on control-channel-safe checks before enable\/auth","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/mcp-control-channel-operations-gate-on-control-channel-safe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### MCP control-channel operations gate on control-channel-safe checks before enable\/auth\n\nEnabling or authenticating an MCP server now says whether it is managed, disabled or unapproved, with the step to take.\n\n`mcp_toggle` (when enabling a server) and `mcp_authenticate` now run a shared block-reason check that can return `managed-policy`, `disabled`, or `unapproved`, each with its own instructive message, replacing the old generic \"blocked by enterprise managed policy\" catch-all. A disabled server now instructs you to run `mcp_toggle` first, and an unapproved server instructs you to approve it in `\/mcp` first.\n\n- Area: MCP\n- Names: `mcp_toggle`, `\/mcp`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}