MCP gateway

Put a policy on every tool your agent can call.

An agent with a raw MCP server can call whatever that server published, including a tool whose description changed since you last read it. Fizzlayer Gateway is the process in between: unmodified agentgateway v1.7, plus fizz-guard for allow, deny, approve, and tool pins.

Self-hosting needs Docker. The hosted shared gateway, Pro machines, Slack approvals, the connect CLI, and OAuth for ChatGPT or Claude are not available yet.

The gap

Three ways a tool call goes wrong.

Unchecked tools

A client that holds the upstream token can call refund, delete, or force-push as easily as it can call a read. Fizzlayer keeps that token on the gateway and applies a rule per tool.

A changed description

A server can rewrite a tool's description after you approved the first version. The pin is a hash of the name, description, and input schema. A new hash is removed from the tool list until you approve it.

Keys in the client

Pasting an upstream API key into Claude or Cursor leaves it on that machine. The control plane stores the key as AES-256-GCM ciphertext. The browser never gets it back.

How it works

Reject, approve, retry once.

The guard does not wait on the phone. Agentgateway's check times out in about 10 seconds, so the call returns immediately.

  1. 1

    List and pin

    tools/list records each tool. Unreviewed tools are hidden by default. You approve the observed hash before a call is allowed.

  2. 2

    Call

    tools/call is allow, deny, or approve. Deny never reaches the upstream server. Approve stores a hash of the arguments and rejects with an id.

  3. 3

    Decide, then the same call

    You set the row to approved or denied in the API, or on the local admin page. The identical call is allowed once. A second retry is rejected. The default window is 10 minutes.

The rejection text is: "Approval required: an approver was notified (id …). Ask the user to approve, then retry the same call." Notifications are a log line, a webhook, or a phone call. Slack is not a channel yet. A phone approval does not collect a keypress. You still approve in the API. If fizz-guard is down, the proxy denies the call.

What the code does

Features you can run.

Many servers, one listener

agentgateway multiplexes HTTP, SSE, and, on a dedicated or self-hosted gateway, stdio. Shared mode refuses stdio. Tool names are not prefixed (prefixMode: never).

Client identity

Clients send Authorization: Bearer with an ES256 JWT. Claims are iss=fizzlayer, aud equal to the gateway URL, sub, ws, and jti. JWKS is public.

Control plane

Signed-in routes under /api/gateway create gateways, servers, policies, pins, approvals, and tokens. A registration token pulls YAML. That pull can contain upstream keys.

Phone calls share a cap

Hobbyist 0, Tinkerer 20, Pro 100, Enterprise unlimited unless a contract sets a cap. Sensor alert calls use the same monthly count. A full cap skips the call and falls back to the webhook or a log line.

Audit rows

fizz-guard writes usage it sees. Plans name 7, 30, or 90 days of retention. Nothing in the current code deletes old rows on that schedule, and tool-call totals are not metered against the plan.

Open source

Apache-2.0, copyright Fizzlayer LLC. agentgateway stays upstream and unmodified. Fizzlayer does not use that project's name as its own brand.

Security model

What the gateway checks, and what it does not.

Security notes in the docs.

Where it runs

Self-host, hosted, or the Pro row.

Self-host, standalone

Clone the repo and run gateway/compose/test.sh. Docker builds fizz-config, fizz-guard, and the sample server, and pulls the pinned agentgateway image. You edit policies in that Postgres. No Fizzlayer account is required for this stack.

Linked to the control plane

fizz-agent pull polls GET /api/gateway/agent/config with the registration token and writes the file agentgateway watches. Standalone mode uses fizz-config against a Postgres you run. Do not point both writers at one config file. Try the linked path with gateway/compose/test-linked.sh.

Hosted and Pro

Hobbyist and Tinkerer are entitled to one shared gateway. Pro is entitled to one dedicated gateway and stdio. Creating that row does not start a machine. There is no hosted MCP URL. Join the list.

Plans

Counts from fizz_plans.

Prices match /pricing. Sensors limits are enforced in the app. Gateway and server counts return 402 from the control plane when you pass them. Tool-call totals are not enforced yet.

Gateway plan limits
Plan Price Gateway MCP servers Tool calls / month Phone calls Audit days on the plan Seats
Hobbyist $0 1 shared 3 10,000, not metered 0 7 1
Pro $25 / month 1 dedicated, not provisioned 25 200,000, not metered 100 90 3
Enterprise Custom Custom Custom Custom Unlimited unless a contract sets a cap Custom Custom

Pro's dedicated flag and stdio flag are on the plan. The API accepts mode: dedicated and a stdio server for that plan, and rejects stdio on a shared gateway. No hosted process is started. Email and webhook alerts are on every plan, including Hobbyist. Phone calls are paid-only and reset on the first of the month (UTC). Stripe Checkout still sells Tinkerer and Pro. It does not meter gateway tool calls.

FAQ

Short answers.

Can I point Claude, Cursor, or ChatGPT at fizzlayer.com today?

Not at a hosted gateway URL. That URL does not exist yet. You can point Claude Code or Cursor at a gateway you run, with a bearer JWT. ChatGPT and the Claude connector directory need an OAuth 2.1 server, which is not built. Sensor data is a different MCP server at /api/mcp.

Does creating an account give me a gateway?

No. /app.html opens Sensors. There is no gateway onboarding screen. The control-plane API can store a gateway for a signed-in user after the gateway migration is applied. That row does not start a proxy.

Where do approvals show up?

Log, webhook, or phone, from the policy's notify_channel. The local stack also has a page on 127.0.0.1:9002 if you set an admin token. Slack and Discord buttons are not implemented.

Is the Gleam app the gateway UI?

The signed-in Gleam app does not include gateway screens. Marketing pages stay static HTML. Gateway setup is the API and the Docker compose file.

What license is the gateway?

Apache-2.0, copyright Fizzlayer LLC. The data plane is upstream agentgateway, also Apache-2.0. Self-hosting the local compose does not need a paid plan.

Run the local stack, or wait for a hosted URL.

Open the quickstart Join the hosted list