Haldir
ExposureGuardLABSCO SUMMARY
One catalogue and one policy point is the answer to having twenty MCP connections and no way to govern them.
The problem this solves appears the moment an organisation has more than a handful of servers: each has its own credential, its own scopes, and no shared record of what was called. A proxy that merges them and enforces policy centrally is the obvious structural fix, and the VPC option means the traffic need not leave your network. Private beta and Enterprise pricing, so this is an architecture decision rather than something to try.
What it is
A gateway rather than a server. It has no native tool catalogue by design: it builds a merged one from the MCP servers your organisation has registered, and applies policy to every call that passes through.
What you get
Whatever your registered downstream servers expose, presented as one catalogue with policy enforced in the middle. Per-direction DLP can be configured, including switched off.
Requirements
An API key. The gateway is an Enterprise feature in private beta; running it inside your own VPC is part of the custom-priced Enterprise plan with SAML SSO, RBAC and SIEM integration.
Setup effort
Paste a URL with a key — add the endpoint to your client
USE CASES
01
Governing many MCP servers at once
Register them behind the gateway and enforce policy in one place.
02
Keeping traffic inside your network
The hybrid deployment runs the gateway in your own VPC.
03
Applying DLP to tool traffic
Per-direction data-loss policy on what flows in and out.
BEFORE YOU INSTALL
What to know first
Requires
- an MCP client that can reach a remote endpoint
- An API key as Authorization: Bearer, prefixed oah_
INSTALLATION
Connect your client
Add the endpoint to your client.
Server setup
ENDPOINT URL
https://api.aisecuritygateway.ai/mcpRequirements
- An API key as Authorization: Bearer, prefixed oah_
