Limit who can pass, attach or impersonate the agent's role
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
Check 3 of 30: Limit who can pass, attach or impersonate the agent's role. Anyone who can attach the agent's role to a new resource can borrow its access without ever being granted it. Limiting that right keeps the agent's permissions from spreading.
The whole checklist ยท The map
Why it matters
Anyone who can attach the agent's role to a new resource can borrow its access without ever being granted it. Limiting that right keeps the agent's permissions from spreading.
How, in each cloud
- AWS
- Grant iam:PassRole only for the specific roles a principal needs to pass to a service.
- Google Cloud
- Grant the Service Account User role only to principals that need to attach the service account to a resource.
- Azure
- none found on 2026-11-10
What the documentation says
- "pass a role to an AWS service, you must grant the PassRole permission to the" (source)
- "The Service Account User role ( roles/iam.serviceAccountUser ) lets a principal" (source)
- Previous: Use short-lived role credentials and no long-lived access keys for the agent
- Next: Scope the role's trust to the specific agent, service account or workload
Related pages
- Scope the role's trust to the specific agent, service account or workload: the check, and how in AWS, Google Cloud and Azure
- Do not run the agent as a default or pre-granted account: the check, and how in AWS, Google Cloud and Azure
- Write the agent's permission policy from what its tools actually call: the check, and how in AWS, Google Cloud and Azure
Sources
- docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_passrole.html, read 10 Nov 2026
- cloud.google.com/iam/docs/service-account-permissions, read 10 Nov 2026
Last reviewed 16 Nov 2026.