{"version":"2.1.239","anchor":"remote-sessions-drop-disallowed-mcp-config-servers-instead-o","canonical_anchor":"remote-sessions-drop-disallowed-mcp-config-servers-instead-o","heading":"Remote sessions drop disallowed --mcp-config servers instead of failing the run","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/remote-sessions-drop-disallowed-mcp-config-servers-instead-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Remote sessions drop disallowed --mcp-config servers instead of failing the run\n\nRemote sessions drop disallowed --mcp-config servers and keep running instead of failing.\n\n**What**\n\nWhen policy blocks servers supplied via `--mcp-config`, a remote session (or a bridge child) now drops just those servers and keeps going. Rejecting the whole run with an error is now limited to non-remote sessions.\n\n**Details**\n\n- Gated by whether the session is remote (`CLAUDE_CODE_REMOTE`) combined with the enterprise MCP policy.\n- Entries recognized as bridge carrier configs are normalized before being scoped as dynamic.\n\n**Evidence**\n\n`dropForSideloadPolicy`\n\n- Area: MCP\n- Names: `--mcp-config`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}