Ranked #3 of 710/18 · Last reviewed
IAM and secrets controls
Identity and access management, secrets managers and short-lived credentials that limit what any process, an agent included, can reach with the developer's identity.
Verdict: Essential blast-radius control, but it governs credentials, not agents.
Who it suits
Every team, as the baseline that limits the blast radius when an agent does something wrong.
ExamplesLeast-privilege roles, short-lived cloud tokens, secrets managers, pre-commit secret hooks
CostVaries by identity provider and secrets manager, and is often already licensed: check your current contracts.
Pairs with
An AASB, which decides what the agent does with the access IAM grants.
How it handles MCP connections- Discovery: Does not see MCP servers.
- Control: Limits what credentials given to an MCP server can reach.
- Record: Provider audit logs of credential use, attributed to the identity.
Strengths
- Limits what a compromised or mistaken agent can reach
- Short-lived tokens shrink the value of leaked secrets
- Cloud and SaaS audit logs record credential use
Limits
- Cannot tell the agent from the developer: the agent inherits the developer's identity
- Does not see or judge commands, files or MCP calls
- Says nothing about which agents run or what they do
Scores, with reasons
Each criterion is scored 0 to 3 as defined on the criteria page.
| Criterion | Score | Why |
|---|---|---|
| Visibility | 1 | Sees credential use at the target system, attributed to the developer, without knowing an agent made the call. |
| Enforcement | 2 | Denies what a credential is not allowed to do, at the resource, for agent and developer alike. |
| Developer friction | 2 | Tight scopes and short-lived tokens add re-authentication and access requests. |
| Coverage of terminal and MCP actions | 1 | Limits what a command or MCP call can reach, but never sees the command or call itself. |
| Audit evidence | 2 | Audit logs at cloud and SaaS providers show what each identity did, not which agent did it. |
| Deployment effort | 2 | Usually in place; tightening scopes for agent use is ongoing work per system. |
| Total | 10/18 | Ranked #3 of 7. See the full table. |