Skip to content
Sentynel

#opinion3 min readBy Sentynel

Every tool an agent can call should start switched off

Uber's agent gateway lists every tool as disabled until the owning team approves it. That is operations design, and most companies skip it.

Share

Most companies give an agent access to a tool and then work out who is responsible for it. Uber's engineering team did it the other way round: in its MCP gateway, every tool starts disabled and only becomes available to agents when the team that owns it has reviewed it and switched it on. The default decides who is accountable.

What Uber published

In its post on the design of its MCP gateway, Uber says the platform hosts "over 800 MCP servers and over 5000 tools". A crawler finds the internal services and generates the tool definitions automatically. Then comes the part worth copying: "Every MCP server and tool starts in a disabled state and must be explicitly reviewed and enabled by the owning team."

Uber also describes owners who can refine the generated definitions, approve every configuration change and roll back to a previous version. Access is checked per tool, for callers that are people, services or agents.

This is Uber's engineering, not a recipe for your company. The idea behind it travels well, though.

Generating tools is easy. Owning them is the work

Turning an API into something an agent can call is now a matter of hours. That is exactly the risk: the catalog grows faster than anyone's understanding of it. A tool that exists but has no named owner is a decision nobody made.

When a tool starts switched off, someone has to look at it before it goes live and ask the questions an operation needs answered:

  • What job does this tool serve, and which process does it belong to?
  • What may it change, and what may it only read?
  • Who gets paged when it does something unexpected?
  • Who decides when it is retired?
A tool's path to an agent
  1. 01DiscoveredGenerated from existing services
  2. 02Switched offDefault state
  3. 03Owner reviewJob, limits, escalation
  4. 04EnabledApproved and versioned

Any change goes back to the owner for approval.

If nobody can answer, the tool stays off. The cost of that is a short delay. The cost of the alternative is an agent acting through a door nobody remembers opening.

Off by default is a design choice, not a security tax

It is tempting to file this under security. We would argue it is operations. A previous piece of ours made the point that a permission you have to revoke later is a design bug. The same logic applies to tools: switching things on after review is cheaper than finding out what was on after an incident.

It also changes who is in the room. Review by the owning team puts the people who run the process in charge of what agents can touch, rather than leaving the choice to whoever built the integration.

A test you can run this week

List every tool your agents can currently call. For each one, write the name of the person who approved it and the process it serves. Count the blanks.

Those blanks are your real backlog. Switch off the ones nobody can claim, let the owners turn on what they need, and write down why. The operation around the agent gets clearer with every tool that has a name next to it.

What would your agents lose tomorrow if every tool without an owner went dark?

Sources

  1. https://www.uber.com/blog/designing-mcp-gateway/
Share
← All sygnals