Skip to main content
If your firewall or Snowflake network policy requires an allowlist, request the current Ruby egress addresses through your support channel. Use the addresses confirmed for your deployment; a provider’s or another deployment’s IP addresses do not apply to Ruby.

When static egress routing applies

Static egress routing requires a configured proxy in the Ruby deployment. When that proxy is configured, it applies to:
  • Remote MCP servers whose hostname belongs to a domain verified for your workspace. For example, mcp.example.com belongs to a verified example.com; a server hosted on a vendor’s different domain does not. Without a verified domain, remote MCP traffic uses the normal outbound route.
  • Snowflake connections, independently of workspace domain verification.
  • BigQuery connections, independently of workspace domain verification.
  • The official BigQuery MCP server (bigquery.googleapis.com), even without a verified domain.
Other connections and tools, including other data warehouse connections, web search, and browsing, do not use this static egress route. Their outbound cloud IP addresses can change.

Configure an allowlist

  1. Confirm that static egress routing is enabled for your Ruby deployment and obtain its current addresses through your support channel.
  2. For a remote MCP server, verify the server’s parent domain under Admin > Security, Domains & SSO tab, under Verified domains.
  3. Add the confirmed addresses to the destination’s network allowlist and test the connection from Ruby.
  4. Keep bearer-token or OAuth authentication enabled on the MCP server.
Use the addresses confirmed for your deployment’s region. An allowlist for a different region will not let Ruby connect.
A source IP identifies an outbound network route, not your workspace or user. Static addresses may be shared across workspaces. An IP allowlist is a network restriction and must not replace authentication.