{"version":"2.1.300","anchor":"managed-mcp-servers-setting-marked-unreadablestandin","canonical_anchor":"managed-mcp-servers-setting-marked-unreadablestandin","heading":"Managed MCP server policy gets special handling when settings cannot be read","tier":"internal","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/managed-mcp-servers-setting-marked-unreadablestandin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Managed MCP server policy gets special handling when settings cannot be read\n\nThe organization policy that controls MCP servers is now marked for special handling when managed settings cannot be read\n\n**Unclear.** What Claude Code does with MCP servers when the managed settings cannot be read is not stated.\n\n**What**\n\nOrganizations can manage Claude Code through managed settings, which are policy files an administrator controls. One of these policies decides which MCP servers (outside tools and data sources Claude Code can connect to) are allowed. That policy is now marked to be handled in a special way when the managed settings cannot be read.\n\n**Why**\n\nThis most likely changes what Claude Code does about MCP servers when it cannot read the organization's policy.\n\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}