MCP policy
⚠️
Preview — this feature is being built; the design below is the spec.
The MCP connector lets a request or an agent call tools on remote MCP servers. An organization’s MCP policy decides which servers are allowed, so a developer cannot connect production data to an unvetted server by accident.
Modes
| Mode | Allowed servers |
|---|---|
open | Any public HTTPS server. The default for new organizations. |
allowlist | Only servers whose URL starts with a listed prefix, and listed tunnels. |
disabled | None. The mcp_servers field is refused. |
With require_tunnel_for_private (on by default), a server whose address resolves to a private network is refused unless it is reached through a tunnel, which closes off requests that try to make Syntic probe internal addresses.
Set it
Console: Settings → Security → MCP servers, or Set the MCP policy.
What developers see
A request naming a server outside the policy fails before any connection with 403 mcp_server_not_allowed, and the message names the policy, not just the failure, so they know whom to ask.
Recommended setup
- Start in
allowlistmode for production workspaces, even if the list is short. - Prefer exact path prefixes (
https://mcp.example.com/crm/) over whole hosts. - Review the list when you review vendors; remove servers nobody calls (the server tools analytics show MCP calls).
Was this page helpful?