{"version":"2.1.300","anchor":"policy-settings-allowedpluginmcpservers-readers-and-platfor","canonical_anchor":"policy-settings-allowedpluginmcpservers-readers-and-platfor","heading":"Admin settings: plugin MCP allowlist reaches Claude Code, egress lists filter by platform","tier":"notice","area":"Managed Settings","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/policy-settings-allowedpluginmcpservers-readers-and-platfor","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Admin settings: plugin MCP allowlist reaches Claude Code, egress lists filter by platform\n\n`allowedPluginMcpServers` is now marked as read by Claude Code, and network endpoint lists now drop entries meant for other platforms\n\n**What**\n\nThree changes to the settings administrators manage:\n\n- `allowedPluginMcpServers` is now marked as read by both the desktop app and Claude Code. MCP servers are extra tools that plugins can connect.\n\n- Lists of allowed outgoing network addresses now leave out any address marked for platforms other than the one you are on.\n\n- One policy setting's description now says that in third-party deployments it also stops Cowork's workspace image and tools from being downloaded ahead of time. They are downloaded when a task first needs them.\n\n**Why**\n\nAdmins can expect `allowedPluginMcpServers` to apply in Claude Code, and network allowlists only include addresses for the machine's own platform.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: yes"}