Skip to content
AI Agent Access Control

Gemini Enterprise agents run as the Agent Runtime identity, so the limits are set there

Gemini Enterprise registers an ADK agent that runs on Agent Runtime, so the agent runs under the Agent Runtime identity described in that entry. Permissions Gemini Enterprise itself grants to a registered agent: none found on 2026-11-10. Google documents that the connection between Agent Runtime and Gemini Enterprise is compliant with VPC Service Controls.

The full map ยท Google Cloud overview

The Gemini Enterprise pages show it acting on Google Cloud resources only through ADK agents hosted on Agent Runtime, so this entry covers that path. A registered agent runs under the Agent Runtime identity. A Gemini Enterprise administrator can see the agent's identity, typically its SPIFFE ID. Permissions Gemini Enterprise itself grants to a registered agent: none found on 2026-11-10.

An agent that must reach Google Cloud resources for a user needs an OAuth client, an authorization resource registered with Gemini Enterprise, and user consent. Who manages agents is set by Gemini Enterprise IAM roles; what the agent can call is set by the Agent Runtime deny and Principal Access Boundary policies. The connection to Agent Runtime is compatible with VPC Service Controls, and Cloud Audit Logs cover administrative and data-access operations.

Status
Documented as Gemini Enterprise. The audit logging page still refers to Cloud Audit Logs for Vertex AI Agent Builder. A page titled Agentspace: none found on 2026-11-10 in the pages read. The Gemini Enterprise pages show it acting on Google Cloud resources only through ADK agents hosted on Agent Runtime, so this entry covers that path. (source)
The identity it runs as
Gemini Enterprise registers an ADK agent that runs on Agent Runtime, so the agent runs under the Agent Runtime identity described in that entry. A Gemini Enterprise administrator can see the agent's identity, typically its SPIFFE ID, or the Agent Registry resource ID if no SPIFFE ID is published. (source)
What it gets by default
Permissions Gemini Enterprise itself grants to a registered agent: none found on 2026-11-10. Registering an ADK agent requires the Gemini Enterprise Admin role for the person doing it; the agent's own Google Cloud access comes from Agent Runtime. (source)
Tools and actions
An agent that must reach Google Cloud resources for a user needs authorization details configured: an OAuth client, an authorization resource registered with Gemini Enterprise, and user consent. Other tool and action behavior sits in the Agent Runtime entry. (source)
The agent's permissions or the user's
Both. ADK agents receive the user's email address from Gemini Enterprise, and an agent that must access Google Cloud resources on behalf of a user needs the authorization details configured. Agent-level access follows the Agent Runtime entry. (source)
Network reachability
Google documents that the connection between Agent Runtime and Gemini Enterprise is compliant with VPC Service Controls. Cross-project ADK agents connect over Google Cloud private networking. (source)
What is logged
Google documents Cloud Audit Logs for administrative and data-access operations on Gemini Enterprise (Vertex AI Agent Builder) resources, viewable in Logs Explorer, with an option to enable Data Access audit logs. Logging of what the agent does inside Google Cloud sits in the Agent Runtime entry. (source)

Boundaries that apply

  • Gemini Enterprise IAM roles. Roles such as Gemini Enterprise Admin, Discovery Engine Editor and Viewer control who manages agents; users with the discoveryengine.agents.manage permission can view a private agent's details but not use it. (source)
  • Agent sharing state. A private agent is meant for personal use and only its creator can chat with it. (source)
  • VPC Service Controls. The Agent Runtime connection is compatible with VPC-SC perimeters. (source)
  • Agent Runtime IAM, deny, PAB. Limits on what the agent can call in Google Cloud are the Agent Runtime boundaries. (source)

Checks to run for Google Cloud

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. cloud.google.com/gemini/enterprise/docs/audit-logging, read 10 Nov 2026
  2. cloud.google.com/gemini/enterprise/docs/register-and-manage-an-adk-agent, read 10 Nov 2026
  3. cloud.google.com/gemini/enterprise/docs/agents-overview, read 10 Nov 2026
  4. docs.cloud.google.com/gemini-enterprise-agent-platform/scale/runtime/agent-ident, read 10 Nov 2026

Last reviewed 16 Nov 2026.