Skip to content
Layer 4 of four

Agents and Automation

Agents are the layer arriving fastest and owned least, from Rovo and Agents in Jira to Forge and MCP connections. Atlas Bench gives them an identity, a scope, and a change record, so an agent is a governed participant rather than an account nobody owns.

Rovo, Agents in Jira, Forge, MCP with Claude and Copilot, agent lifecycle, usage and cost governance.

source build review deploy run scope check built inside the permission model, not beside it L1 L2 L3 L4

The problem

Agents are being adopted the way tools always are, one team at a time, ahead of any decision about who owns them. An agent gets access because a person granted it, runs against a budget nobody is tracking, and produces work that enters the same queues as human work with no way to tell the difference afterwards.

The layer is new, the failure mode is not. It is the same shape as unmanaged integrations and unmanaged accounts, arriving faster and with more autonomy. What makes it tractable is that the three layers underneath already answer most of it. An agent needs an identity, a platform to act in, and a change record. Where those exist, an agent is a governed participant. Where they do not, it is another account nobody owns.

The Atlas Bench team provided valuable insights and resources that accelerated our Forge development. Their expertise helped us build custom solutions faster and engage more deeply with the Atlassian ecosystem.

Jason Mueller Jason Mueller Sr. Atlassian Systems Engineer

What we work in at this layer.

Atlassian

AWS

Microsoft Azure

Anthropic

what one agent registration looks like
agent        release-notes-drafter
identity     own account, scim provisioned
acts in      jira, confluence
scope        read all, write to one space
budget       owned by platform engineering, capped
record       every action attributed and retained with the change

Find out what an agent would inherit.

Fixed scope. The assessment reads the three layers an agent lands on, identity, platform and governance, before anything is switched on. You get the findings, the ownership gaps, and the order to close them in.