Product · MCP Gateway

One boundary in front of every MCP tool call.

In development, not yet available. The gateway sits in front of your MCP servers under the stateless 2026-07-28 MCP specification: it validates each request’s routing headers against its body, inspects the tool call before it is forwarded, and carries trace context through to the tool — with no session store.

Govern → Enforce → Prove

In development

01

Govern

The same policy pack, applied to every MCP server behind the gateway, with the approved tools and their schemas pinned.
02

Enforce

Arguments checked against the tool’s own schema and the pack before the call is forwarded; an unapproved tool or a tampered call is refused with a machine-readable code.
03

Prove

Allowed and refused calls sealed in the ledger with their trace id, so the request, the decision and the tool’s execution correlate end to end.

Status: in development. What ships today for MCP is PRAE’s own MCP server, which gates file access for any MCP-capable agent — see MCP server integration.

MCP & MCP servers →