# Write the agent's permission policy from what its tools actually call

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

Check 6 of 30: Write the agent's permission policy from what its tools actually call. Broad starter policies make every tool call possible, including ones nobody planned. A policy limited to the real calls limits what a wrong or hijacked call can do.

## Why it matters

Broad starter policies make every tool call possible, including ones nobody planned. A policy limited to the real calls limits what a wrong or hijacked call can do.

## How, in each cloud

- **AWS:** Start from the documented minimum policy and narrow it; AWS says to use broad deployment permissions only for development and testing.
- **Google Cloud:** Grant the agent identity only the roles its code needs; Google describes agent identity as enabling a least-privilege approach.
- **Azure:** Grant the least privilege needed and avoid broader roles at broader scopes.

## What the documentation says

- "Use broad deployment permissions only for development and testing." ([source](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-permissions.html))
- "Agent identity provides a per-agent identity that enables a least-privilege" ([source](https://docs.cloud.google.com/gemini-enterprise-agent-platform/scale/runtime/agent-identity))
- "When planning your access control strategy, it's a best practice to grant users the least privilege to get their work done." ([source](https://learn.microsoft.com/en-us/azure/role-based-access-control/best-practices))

- [Previous: Do not run the agent as a default or pre-granted account](/checklist/no-default-accounts/)
- [Next: Set an organization-level ceiling the agent's role cannot exceed](/checklist/set-permission-ceiling/)

## Related pages

- [Set an organization-level ceiling the agent's role cannot exceed: the check, and how in AWS, Google Cloud and Azure](/checklist/set-permission-ceiling/)
- [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/)

## Sources

- docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-permissions.html: https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-permissions.html (read 10 Nov 2026)
- docs.cloud.google.com/gemini-enterprise-agent-platform/scale/runtime/agent-ident: https://docs.cloud.google.com/gemini-enterprise-agent-platform/scale/runtime/agent-identity (read 10 Nov 2026)
- learn.microsoft.com/en-us/azure/role-based-access-control/best-practices: https://learn.microsoft.com/en-us/azure/role-based-access-control/best-practices (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://aiagentaccesscontrol.com/checklist/least-privilege-policy/
