Skip to content
AI Agent Access Control

8 agent platforms, and the identity each one runs as

The map covers 8 ways to run an AI agent in a cloud account: 5 managed agent platforms and 3 self-hosted patterns, one per cloud. Each page gives the identity the agent runs as, what it gets by default, how its tools are called, its network paths and its logs, from provider documentation.

The full map ยท The checklist

Where Act is behind

Act draws the boundary at the access layer (cloud IAM and network controls, and the gateways or MCP servers in front of agents); it does not inspect prompts or model outputs, which needs a different tool. Your team applies the boundaries it proposes, and its customer evidence for AI boundaries is less mature than for its core access control.

Last reviewed 16 Nov 2026.