Skip to main content

Agent access model

For now, in non-production, an agent works with the privileges of the developer who runs it. Production stays with people.

An agent never has more access than the person that it acts for. In integration, each agent also has its own identity, so the approval record names the agent.

Current status

The rule is live for the production guard. Agent identity, the refusal of proven agents after integration and the approval record are in integration. The MCP production route does not run yet. We plan a cap for one agent, and we defer it for now.

The rule​

access(agent) = access(person) ∩ ceiling(agent)
  • access(person) is what the person can do. For now, in non-production, this is the tier of the person for each project and environment.
  • ceiling(agent) is what an agent may do. It excludes each operation that only a person may do.
  • The symbol ∩ means the overlap. The agent gets only what is in both areas.

Press Play to see the rule in five steps. The last step shows a cap for one agent. We plan that cap.

The access model of an agentTwo areas that overlap. The left area is the access of the person. The right area is the ceiling of the agent. The overlap is the access of the agent. Step 1: Start with the person. Step 2: Add the ceiling of the agent. Status: In integration. Step 3: The agent gets the overlap. Status: Live. Step 4: Production stays with people. Status: In integration. Step 5: A cap for one agent. Status: Planned.Access of the personaccess(person)Ceiling of the agentceiling(agent)In integrationAccess of the agentaccess(agent)Rule: live for the production guardThe agent works hereCap: read only (Planned)Approve a stageafter integrationStart areleaseRefused for a proven agentIn integrationRead withMCP toolsOpen apull requestAccess that theperson does not haveNot granted
The access model of an agentTwo areas that overlap. The left area is the access of the person. The right area is the ceiling of the agent. The overlap is the access of the agent. Step 1: Start with the person. Step 2: Add the ceiling of the agent. Status: In integration. Step 3: The agent gets the overlap. Status: Live. Step 4: Production stays with people. Status: In integration. Step 5: A cap for one agent. Status: Planned.Access of the personaccess(person)Ceiling of the agentceiling(agent)In integrationAccess of the agentaccess(agent)Rule: live for the production guardThe agent works hereCap: read only (Planned)Approve a stage after integrationStart a releaseRefused for a proven agentIn integrationRead with MCP toolsOpen a pull requestAccess that the person does not haveNot granted
All 5 steps

The access of an agent is the overlap of the access of its person and the ceiling of the agent. Production stays with people.

Status tags​

Each part of the model in the table has a status tag. The tag tells you what exists today.

  • LiveMerged. It runs, or a release includes it.
  • Partly liveSome parts are live. Each part shows its own status.
  • In integrationMerged. It rolls out to the integration environment.
  • PlannedDesigned or listed. Not built.

The parts of the model​

The parts of the access model
PartStatusWhat it does
The ruleLiveAn agent never has more access than its person: access(agent) = access(person) ∩ ceiling(agent).Live for the production guard.
Agent identityIn integrationEach agent has its own identity. Each caller assertion carries a signed agent_id: mcp-client:<id>, beck or mcp-shim.
Production stays with peopleIn integrationOnly a person can start, approve, reject, retry or roll out a stage after integration, or start a release. Infrastream refuses any proven agent, an assertion caller or an IAP service account.
The approval recordIn integrationApproval rows record who acted and through which agent (ActorClass and AgentId).
Each MCP client is an agentIn integrationEvery MCP client counts as an agent. A human action needs the portal.
MCP access by tierIn integrationSign-in needs an organization tier. The gcp mode gives 10 read-only metadata tools under per-tier reader accounts.It runs in the integration environment. The MCP production route does not run yet.
Writes are pull requestsLiveAgents write only through pull requests (write_pr). CI and the reconciler review them.
A cap for one agentPlannedA lower ceiling for one agent, for example read only.Deferred for now.

Agents use the privileges of their developer​

For now, in non-production, an agent works with the privileges of the developer who runs it. These are the privileges of the person: the tier for each project and environment. For now, an agent does not get privileges of its own.

Infrastream defers the items below.

  • Beck route tokens.
  • An agent GitHub bot.
  • A cap for one agent.

Agents write only through pull requests, with the write_pr tool. CI and the reconciler review each pull request.

Production is for people​

In integration, Infrastream refuses any proven agent that starts a release. It also refuses a proven agent that starts, approves, rejects, retries or rolls out a stage after integration. Only a person can do these actions.

A proven agent is a caller with a signed assertion, or an IAP service account.

Every MCP client counts as an agent. For a human action, use the portal. The MCP gives access by tier. Sign-in needs an organization tier.

The gcp mode of the MCP gives 10 read-only metadata tools. It uses per-tier reader accounts. This access runs in the integration environment. The MCP production route does not run yet.

The record names the agent​

Each agent has its own identity. Each caller assertion carries a signed agent_id. The agent_id has one of these forms: mcp-client:<id>, beck or mcp-shim.

Approval rows record who acted and through which agent. The fields are ActorClass and AgentId. This record is in integration.

Example: a database administrator with two agents​

The example shows the rule. It does not list the tools that exist today. A database administrator uses the portal and two MCP clients. Both clients act for the person.

A database administrator with two agents
ActionThe person, in the portalAn MCP client of the personA second MCP client, with a read-only cap (Planned)
A database action that a tool offersAs the tier of the person allowsAs the tier of the person allowsRead actions onlyPlanned
Approve a stage after integrationYesNo. The portal refuses a proven agent.In integrationNo. The portal refuses a proven agent.In integration
The name in the signed call of an MCP clientNot applicableThe person and the agent mcp-client:AIn integrationThe person and the agent mcp-client:BIn integration

Each client has its own agent ID, so the signed call names the person and the agent. Each call carries a signed assertion, so both clients are proven agents. The portal refuses a proven agent that approves a stage after integration. We plan a cap for the second client. With the cap, it can only read.

Next​