Unbind

Limiting Access

Keep an agent inside the teams and projects you pick.

An agent is a program that makes its own decisions, some of them wrong. Give it the access you would give a new colleague on their first day, not your own.

The three controls

Whether you connect with OAuth or an API key, you pick the same three things:

  • Role: what the agent can do.
  • Access: where it can do it.
  • Privileges: what it can read.

Role

RoleGood for
ViewerQuestions: "what is deployed where?". The agent gets no tools that change anything.
EditorReal work: deploy, change settings, set variables. Cannot delete.
AdminAlso deletes. Rarely needed.

Start with viewer. Move to editor when you want the agent to fix what it finds. With a viewer connection the changing tools are not even offered, so the agent cannot try them.

Privileges

Every privilege is off by default, whatever the role. Switch one on only when the agent's job needs it.

PrivilegeWhat the agent gets
Read variable valuesThe values behind variable names. Without it, list-variables returns names and references only, and the agent can still set values and wire references.
Read logsThe query-logs tool. Without it the tool is not offered at all. Debugging a failed deployment needs this one.
Read webhook URLsThe URLs of webhooks. Without it the webhook tools work but return the URL blank.

Access

Pick Only specific resources and choose the project, environment or service the agent works on. Everything else does not exist as far as the agent can tell: other projects answer "not found".

A good default is editor on one project's staging environment.

Things an agent can never do

No matter the role, a connected agent cannot:

  • Create API keys or approve other apps.
  • Change system settings or update Unbind.
  • Open a terminal in a service.
  • Read or change webhook URLs and S3 credentials.
  • Do more than you can.

Secrets

Deploying does not need to read secrets, so leave Read variable values off unless the agent has to inspect what a variable holds. With it on, values pass through the model's provider. Logs often carry the same secrets, and user data, so treat Read logs the same way.

Hiding values is not a wall. An editor can still write a reference to another service's variable, deploy, and read the result. For anything that must not reach a model, point the agent at an environment that holds no production secrets.

Check what an agent has

Ask it to call whoami. The answer shows the role, the exact resources and the privileges of the connection.

Your avatar > Account Settings > Connected Apps shows every app, what it may do and when it was last used. Revoke cuts it off at once. API keys work the same way under API Keys.

On this page