Skip to content
AI Agent Access Control

What an AI agent can access in Google Cloud, and the controls that bound it

In Google Cloud, an AI agent runs as a service account or a per-agent identity, and can reach whatever that identity's permissions and the network allow. The map covers 3 ways to run one: Agent Runtime on Gemini Enterprise Agent Platform; Gemini Enterprise; Self-hosted agent on Google Cloud Run or GKE.

The map ยท The checklist

In Google Cloud the agent is an agent identity on Agent Runtime, or a service account on Cloud Run or GKE. Agent Runtime lets you choose between a per-agent identity and a shared service account, and the checklist asks for the per-agent one (ab-01). The default Compute Engine service account might hold the Editor role, so ab-05 enforces the constraint that stops that grant.

The ceiling is a Principal Access Boundary policy (ab-07) and an IAM deny policy that targets agent identities (ab-08). VPC Service Controls and Private Service Connect bound data and egress (ab-13, ab-15). Cloud Audit Logs record Admin Activity always, while Data Access logs are off by default for most services and must be enabled (ab-27, ab-28).

Agent platformRuns asNetwork
Agent Runtime on Gemini Enterprise Agent Platform (formerly Vertex AI Agent Engine, Agent Builder)Google documents three choices: a per-agent IAM agent identity (recommended, a principal tied to the individual agent); the Google-managed AI Platform Reasoning Engine Service Agent used by default; or a custom service account.Google documents that the agent runs in a Google-managed network without access to your VPC unless you configure a Private Service Connect interface, which gives private egress to your VPC and on-premises resources.
Gemini Enterprise (agents hosted on Agent Runtime)Gemini Enterprise registers an ADK agent that runs on Agent Runtime, so the agent runs under the Agent Runtime identity described in that entry.Google documents that the connection between Agent Runtime and Gemini Enterprise is compliant with VPC Service Controls.
Self-hosted agent on Google Cloud Run or GKECloud Run runs the service as a service account (the Compute Engine default service account if you do not choose one).Cloud Run can send egress traffic to a VPC network with Direct VPC egress (recommended) or a VPC connector, giving access to resources with internal IP addresses.

The checklist, Google Cloud column

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.

Sources

  1. docs.cloud.google.com/gemini-enterprise-agent-platform/build/runtime/setup, read 10 Nov 2026
  2. docs.cloud.google.com/gemini-enterprise-agent-platform/scale/runtime/deploy-an-a, read 10 Nov 2026
  3. docs.cloud.google.com/gemini-enterprise-agent-platform/scale/runtime/agent-ident, read 10 Nov 2026
  4. docs.cloud.google.com/gemini-enterprise-agent-platform/govern/identity-delegatio, read 10 Nov 2026
  5. docs.cloud.google.com/gemini-enterprise-agent-platform/scale/runtime/private-ser, read 10 Nov 2026
  6. docs.cloud.google.com/gemini-enterprise-agent-platform/machine-learning/general/, read 10 Nov 2026
  7. docs.cloud.google.com/gemini-enterprise-agent-platform/scale/runtime/logging, read 10 Nov 2026
  8. docs.cloud.google.com/gemini-enterprise-agent-platform/scale/runtime/manage-agen, read 10 Nov 2026
  9. cloud.google.com/gemini/enterprise/docs/audit-logging, read 10 Nov 2026
  10. cloud.google.com/gemini/enterprise/docs/register-and-manage-an-adk-agent, read 10 Nov 2026

Last reviewed 16 Nov 2026.