Skip to content
AI Agent Access Control

Explicitly deny the agent IAM changes and destructive actions

Check 8 of 30: Explicitly deny the agent IAM changes and destructive actions. An agent that can edit roles or delete data can widen its own access or cause damage no review would have approved. An explicit deny wins over any allow added later by mistake.

The whole checklist ยท The map

Why it matters

An agent that can edit roles or delete data can widen its own access or cause damage no review would have approved. An explicit deny wins over any allow added later by mistake.

How, in each cloud

AWS
Use an SCP or permissions boundary whose maximum excludes IAM write actions and destructive calls on protected resources.
Google Cloud
Use an IAM deny policy that targets agent identities; Google's example denies all agents in an organization from creating roles and deleting buckets.
Azure
Use deny assignments to block specific actions even if a role assignment grants them.

What the documentation says

  • "policy to set the maximum permissions that an identity-based policy can grant to an IAM" (source)
  • "Identity and Access Management (IAM) deny policies let you set guardrails on access to" (source)
  • "// Deny policy (deny all agents across the org from ability to create or delete buckets)" (source)
  • "Customer-managed deny assignments are currently in private preview." (source)

Sources

  1. docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html, read 10 Nov 2026
  2. cloud.google.com/iam/docs/deny-overview, read 10 Nov 2026
  3. docs.cloud.google.com/gemini-enterprise-agent-platform/scale/runtime/agent-ident, read 10 Nov 2026
  4. learn.microsoft.com/en-us/azure/role-based-access-control/deny-assignments, read 10 Nov 2026

Last reviewed 16 Nov 2026.