{"version":"2.1.116","anchor":"web-search-connector-isolation-policy","canonical_anchor":"web-search-connector-isolation-policy","heading":"Web Search \/ Connector Isolation Policy","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.116\/e\/web-search-connector-isolation-policy","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.116","markdown":"### Web Search \/ Connector Isolation Policy\n\n**What**\n\nOrganizations can now enforce web search and connector isolation policies that restrict MCP connector access within sessions.\n\n**Details**\n\n- When isolation is active, affected sessions see: \"Connectors are unavailable in this session under your organization's web search \/ connector isolation policy. Start a new session to use connectors.\"\n- Web search similarly blocked with a parallel message\n- Isolation is enforced via an isolation latch that checks against a whitelist of MCP commands\n- Gated by `enforce_web_search_mcp_isolation` feature flag\n\n**Evidence**\n\nIsolation message (search for `\"Connectors are unavailable in this session\"`) \u2014 `d41()` at line ~419266"}