# Set an organization-level ceiling the agent's role cannot exceed

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

Check 7 of 30: Set an organization-level ceiling the agent's role cannot exceed. A role policy can be edited by whoever manages that account, so it is a weak limit by itself. A ceiling set higher in the hierarchy holds even if the role's own policy is widened.

## Why it matters

A role policy can be edited by whoever manages that account, so it is a weak limit by itself. A ceiling set higher in the hierarchy holds even if the role's own policy is widened.

## How, in each cloud

- **AWS:** Apply SCPs, which specify the maximum available permissions for IAM roles in the organization, and permissions boundaries on the agent's role.
- **Google Cloud:** Use Principal Access Boundary policies to define the resources the agent's principal may access.
- **Azure:** Use deny assignments, which block listed actions even when a role assignment grants them (customer-managed deny assignments are documented as private preview), and apply governance conditions at management group scope.

## What the documentation says

- "specify the maximum available permissions for the IAM users and IAM roles in your organization." ([source](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html))
- "policy to set the maximum permissions that an identity-based policy can grant to an IAM" ([source](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html))
- "Principal Access Boundary (PAB) policies let you define the resources that" ([source](https://cloud.google.com/iam/docs/principal-access-boundary-policies))
- "Customer-managed deny assignments are currently in private preview." ([source](https://learn.microsoft.com/en-us/azure/role-based-access-control/deny-assignments))
- "above subscriptions. When you organize subscriptions into management groups, the governance conditions that you apply" ([source](https://learn.microsoft.com/en-us/azure/governance/management-groups/overview))

- [Previous: Write the agent's permission policy from what its tools actually call](/checklist/least-privilege-policy/)
- [Next: Explicitly deny the agent IAM changes and destructive actions](/checklist/deny-iam-changes-and-destructive-actions/)

## Related pages

- [Explicitly deny the agent IAM changes and destructive actions: the check, and how in AWS, Google Cloud and Azure](/checklist/deny-iam-changes-and-destructive-actions/)
- [Compare the agent's granted permissions with what it used and remove the rest: the check, and how in AWS, Google Cloud and Azure](/checklist/remove-unused-permissions/)
- [Grant roles at the narrowest scope that works: the check, and how in AWS, Google Cloud and Azure](/checklist/narrowest-scope/)

## Sources

- docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.htm: https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html (read 10 Nov 2026)
- docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html: https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html (read 10 Nov 2026)
- cloud.google.com/iam/docs/principal-access-boundary-policies: https://cloud.google.com/iam/docs/principal-access-boundary-policies (read 10 Nov 2026)
- learn.microsoft.com/en-us/azure/role-based-access-control/deny-assignments: https://learn.microsoft.com/en-us/azure/role-based-access-control/deny-assignments (read 10 Nov 2026)
- learn.microsoft.com/en-us/azure/governance/management-groups/overview: https://learn.microsoft.com/en-us/azure/governance/management-groups/overview (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://aiagentaccesscontrol.com/checklist/set-permission-ceiling/
