MCP gateway
Agents use your tools only where you allow.
Each agent acts as the person who asked, reaches only the tools on its list, and every call is logged.
- About 3 weeks
- to live on real traffic
- Founder-led
- no handoff to juniors
- Fixed price
- agreed before work starts
| Time | Agent | Tool | Action | Result |
|---|
| 09:14:19 | Meeting notes | Calendar | read events | Allowed |
| 09:14:05 | Sales assistant | CRM | update deal stage | Held for approvalAllowed once |
| 09:14:03 | Company search | Docs | search pages | Allowed |
| 09:14:02 | Support triage | Tickets | read ticket | Allowed |
| 09:13:58 | Code review | Repos | read pull request | Allowed |
| 09:13:55 | Invoice matching | ERP | read purchase order | Allowed |
| 09:13:51 | Support triage | send outside Acme | Blocked | |
| 09:13:47 | Text to SQL | Warehouse | run read query | Allowed |
| 09:13:44 | Company search | Drive | list files | Allowed |
| 09:13:40 | Code review | Repos | comment on line | Allowed |
| 09:13:36 | Support triage | Tickets | add internal note | Allowed |
Writes that need a person show here before they run.
- Agent
- Sales assistant
- Tool
- CRM, update deal stage
- Change
- Deal 4471 Proposal to Won
- Approver
- Sales ops lead
Every team connects its agents to tools its own way
Nobody approved the list, the agents act with shared service keys, and when a record changes nobody can say which agent changed it or for whom.
of companies say their AI agents took actions nobody intended.
Sourcesilicon.co.uk
of organizations have a policy to secure their AI agents.
Sourcesilicon.co.uk
of tested tool servers had command injection flaws.
Sourceequixly.com
No agent touches a tool until the allow-list says it may.
| What changes | Without it | With it |
|---|---|---|
| Tools | Each team adds its own servers. | One list, approved by an owner. |
| Access | Agents act with a shared key. | Each call runs as the person asking. |
| Audit | No record of what an agent did. | A log entry for every call. |
What we build
What changes for your teams. We pick the tools to fit the systems you already run.
| Time | Agent | Tool | Action | Result |
|---|
| 09:14:19 | Meeting notes | Calendar | read events | Allowed |
| 09:14:05 | Sales assistant | CRM | update deal stage | Held for approvalAllowed once |
| 09:14:03 | Company search | Docs | search pages | Allowed |
| 09:14:02 | Support triage | Tickets | read ticket | Allowed |
| 09:13:58 | Code review | Repos | read pull request | Allowed |
| 09:13:55 | Invoice matching | ERP | read purchase order | Allowed |
| 09:13:51 | Support triage | send outside Acme | Blocked | |
| 09:13:47 | Text to SQL | Warehouse | run read query | Allowed |
| 09:13:44 | Company search | Drive | list files | Allowed |
| 09:13:40 | Code review | Repos | comment on line | Allowed |
| 09:13:36 | Support triage | Tickets | add internal note | Allowed |
| Time | Agent | Tool | Action | Result |
|---|
| 09:14:19 | Meeting notes | Calendar | read events | Allowed |
| 09:14:05 | Sales assistant | CRM | update deal stage | Held for approvalAllowed once |
| 09:14:03 | Company search | Docs | search pages | Allowed |
| 09:14:02 | Support triage | Tickets | read ticket | Allowed |
| 09:13:58 | Code review | Repos | read pull request | Allowed |
| 09:13:55 | Invoice matching | ERP | read purchase order | Allowed |
| 09:13:51 | Support triage | send outside Acme | Blocked | |
| 09:13:47 | Text to SQL | Warehouse | run read query | Allowed |
| 09:13:44 | Company search | Drive | list files | Allowed |
| 09:13:40 | Code review | Repos | comment on line | Allowed |
| 09:13:36 | Support triage | Tickets | add internal note | Allowed |
Measured against where you started
What changes at a company like Acme Inc
Illustrative figures, not a client result. Your own baseline is taken in the first week.
How others built it
Another company built the same kind of system and wrote publicly about how it went.
- UberDesigning MCP Gateway: Uber’s MCP management platform
What they learned
One gateway can put every agent’s tool calls behind an approved list, the user’s identity and a log.
Hosting over 800 MCP servers and over 5,000 tools.
Everything runs in your cloud, and stays yours
You own the config, the tests and the runbooks, so you can swap any part later.
An allow-list of approved tools, each with a named owner.
| Time | Agent | Tool | Action | Result |
|---|
| 09:14:19 | Meeting notes | Calendar | read events | Allowed |
| 09:14:05 | Sales assistant | CRM | update deal stage | Held for approvalAllowed once |
| 09:14:03 | Company search | Docs | search pages | Allowed |
| 09:14:02 | Support triage | Tickets | read ticket | Allowed |
| 09:13:58 | Code review | Repos | read pull request | Allowed |
| 09:13:55 | Invoice matching | ERP | read purchase order | Allowed |
| 09:13:51 | Support triage | send outside Acme | Blocked | |
| 09:13:47 | Text to SQL | Warehouse | run read query | Allowed |
| 09:13:44 | Company search | Drive | list files | Allowed |
| 09:13:40 | Code review | Repos | comment on line | Allowed |
| 09:13:36 | Support triage | Tickets | add internal note | Allowed |
Sign-in, so every call runs as the person asking.
A log of every tool call, and the tests that prove the rules.
A runbook your platform team owns.
Typical building blocks: agentgateway with the official MCP Registry schema; OAuth 2.1 and the stateless 2026-07-28 spec; tools off until enabled.
Alternatives: IBM ContextForge; Cloudflare MCP portals.
Live in about 3 weeks
The work happens in your cloud, with the people who will own it.
- Week 1Find every tool server your agents reach and who owns it.
- Week 2Put the gateway in your cloud, connect sign-in and move the first agents onto it.
- Week 3The allow-list, the logs and the approval step live, then hand over the runbook.
- After thatRunning on real traffic
Agents reach tools only through an allow-list.
Before we start
- Admin access to one cloud account and to your identity provider.
- A list of the tool servers your agents use, or an hour with whoever knows.
- A named owner for the allow-list, about 3 hours a week.
Is this the right first build?
It fits when
- Agents connect to tools nobody approved.
- Nobody can say what an agent did.
- A team on your side will own it after we leave.
It does not fit when
- You want a hosted tool picked and resold to you.
- You want a strategy deck in place of working software.
- Nobody on your side can own it after we leave.
What’s included and what isn’t
Included
- One gateway in one cloud account.
- Up to 10 existing tool servers behind the allow-list.
- Sign-in through one identity provider.
- Up to 3 agents moved onto it.
Not included
- Writing new tool servers.
- Fixing flaws inside the tool servers themselves.
- A second identity provider.
About 3 weeks. You get a price range before the call and one fixed number after it. That number is the invoice.
- If the work takes longer than we planned, we absorb the cost.
- You pay 50% at the start and 50% at acceptance. Builds of 6 weeks or more pay 40% at the start, 30% at the midpoint and 30% at acceptance.
- If a build starts within 60 days of your Audit results, the full Audit fee comes off its price.
- We start three new projects a quarter, so your start date depends on when you book.
Questions teams ask before they book
Which gateway do you use?
We pick the one that fits the systems you already run. You own the config, the tests and the runbooks, so you can swap any part later. Most often agentgateway with the official MCP Registry schema; IBM ContextForge or Cloudflare MCP portals when they fit better.
Does it run in our cloud?
Yes. The gateway, its logs and its list of approved tools stay in your cloud account.
What does acting as the user mean?
The agent signs in as the person who asked, through OAuth 2.1, so it can reach only what that person may reach.
Do our existing tool servers still work?
Yes. They sit behind the gateway, and agents change only the address they call.
How is a new tool approved?
Someone asks for it, a named owner reviews it and it is switched on in the config. Every tool starts switched off.
Do we need the LLM gateway first?
No. They work well together: the LLM gateway governs model calls and this one governs tool calls.
MCP gateway, running in your cloud in about 3 weeks.
Agents reach tools only through an allow-list. You own the config, the tests and the runbooks.