{"version":"2.1.228","anchor":"managed-settings-mcp-server-entries-are-kept-instead-of-disc","canonical_anchor":"managed-settings-mcp-server-entries-are-kept-instead-of-disc","heading":"Managed-settings MCP server entries are kept instead of discarded","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/managed-settings-mcp-server-entries-are-kept-instead-of-disc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Managed-settings MCP server entries are kept instead of discarded\n\nA malformed MCP servers block in managed settings is kept with a warning, not silently dropped.\n\n**What**\n\nWhen a policy-managed settings file has an MCP servers field that is not the expected shape, the field is now kept and a warning is logged, instead of the whole field being silently removed with \"This field was ignored.\"\n\n**Details**\n\n- Applies to the policy settings path only; other settings validation still drops invalid fields as before.\n\n**Evidence**\n\n`mcpServerEntrySalvageOnly`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}