All posts
Product5 min read

3,000 tools, one broker

Why connectors should be brokered server-side, and what changes when credentials never enter the sandbox.

Nimind Team

Engineering

An agent that can reach your tools is useful. An agent holding your OAuth tokens inside a sandbox is a liability with a nice interface.

The sandbox should not hold keys

Every tool call goes through a broker that holds the credential, checks the agent’s role, and forwards only the request the agent asked for. The sandbox sees a tool name and a payload. It never sees the secret.

Two consequences. A compromised sandbox has nothing worth stealing. And revoking access is one action in one place, not a search through containers you forgot were running.

What the broker buys you

  • One place to revoke a connection for every agent at once.
  • A per-agent allowlist, so the research agent cannot send mail.
  • A log of the arguments as well as the tool name, which is what you need when something looks wrong.
  • Credentials that rotate without touching a prompt or a skill.

The cost

A broker is another hop, another service to keep up, and one more thing that can be down on a Monday morning. It is still the right trade for company work, because the alternative is teaching every agent to handle every secret and hoping none of them is ever careless.

Published September 17, 2026 · Nimind Team

Back to all posts