Skip to main content
Agents reach external tools through the MCP gateway. This page covers per-agent connector and tool permissions — what an agent may do once running, independent of who can chat with it.

Two layers, checked in order

  1. Reachability — can the calling user reach the connector at all? They can if they own it, it’s shared with them (by username, or on Pro and Enterprise with an org unit they belong to — see below), or it’s a platform-managed integration they’ve connected their own account to. A connector that fails this check is invisible — it doesn’t appear in the tool list.
  2. Per-agent permission — is the connector enabled for this agent, and is the specific tool allowed?
Layer 2 is only consulted if Layer 1 passed. Reachability is re-evaluated on every call, never cached past a permission change.

No configuration means fully allowed

Per-agent permission is default-allow. Sharing a connector with someone makes it usable on every agent they run, immediately. A permission row exists only to restrict: disable a connector for one agent, or apply a rule to its tools. Rules are glob patterns against tool names:
The connector stays enabled, but every SEND_ tool is blocked, reads are allowed, and deletes need approval.

Configuring it

Example body for the PUT:
Configuring requires the ability to manage the agent (owner or superuser), or reachability to a connector already attached to it. The narrower path lets someone with a shared connector adjust it without gaining other control over the agent.

Sharing a connector with an org unit

Plans: Pro and Enterprise. Self-hosted: Enterprise license.
On a self-hosted open-source server, connector sharing (see MCP connector-sharing routes) covers public, per-user, and per-agent shares. Owners share by username through the MCP connector-sharing routes. On Pro and Enterprise, and on a self-hosted Enterprise server, the connector owner or an admin can also share it with an org unit. A unit grant reaches everyone in that unit and in every unit beneath it. Share from the connector’s Access tab in the dashboard, or with the API:
To see who uses a connector:
Revoking a share also deletes the grantee’s stored credential for that connector. A later re-grant starts from a clean reconnect.