Skip to content
AI Agent Access Control

An agent on Agent Runtime can run as its own agent identity, the default service agent or a shared service account

Agent Runtime, formerly Vertex AI Agent Engine, lets an agent run as a per-agent identity, a Google-managed service agent or a custom service account. This guide compares the three, the roles each starts with, how to write the principal in a policy, and what a Private Service Connect interface adds.

See the ranking ยท All guides

The product has a new name and the old names remain in places

Google renamed the product that was Vertex AI Agent Engine in the Agent Builder documentation. The old URLs redirect to the Gemini Enterprise Agent Platform documentation, where it is called Agent Runtime, and some role names still read Vertex AI Agent Engine. Google also labels some features Preview or Pre-GA on these pages, so check the label before relying on a behavior. When a ticket says "the Vertex agent's service account", find out which of the three identities below is meant, because the answer changes who else shares the grants. Gemini Enterprise agents that you register run under the Agent Runtime identity described here. Agent Runtime is documented as the place where an agent receives a runtime identity, a network position and logs, so the three guides on identity, network and logging apply to it directly.

Google creates and manages service agents, and they are not listed by default on the IAM page. That makes the default hard to see in a review, so ask for the role grants of the Reasoning Engine Service Agent explicitly rather than assuming it holds nothing. Google documents these choices for an agent on Agent Runtime. Ask the builder for the identity in writing, and check it against the setting in the console.

  • Agent identity: a per-agent IAM principal, which Google recommends. It is tied to the lifecycle of the agent and, Google says, is a more secure principal than a service account.
  • The AI Platform Reasoning Engine Service Agent: a Google-managed service agent, used by default if you choose nothing.
  • A custom service account: shared across every agent you deploy with it, and likely to need the Agent Platform User role plus whatever roles your code requires.

Agent identity starts small and is named in policies by principal

With agent identity, Google documents that the agent starts with the Agent Default Access role, which covers basic project-wide logging and model calling, and the Agent Context Editor role, limited to its own sessions, memories and sandboxes. Further grants are made to a principal written as principal://agents.global.org-ORGANIZATION_ID.system.id.goog/resources/aiplatform/projects/PROJECT_NUMBER/locations/LOCATION/reasoningEngines/AGENT_ENGINE_ID. Google warns that granting roles to the wrong principal produces permission errors. Once IAM is configured, Application Default Credentials in the Agent Platform SDK use the agent identity. Each grant to that principal is a deliberate choice, which is the point of having a per-agent identity: the list of its roles is the list of what this one agent can reach.

Deny policies can target agent identities as a group

Google's agent identity page includes a deny policy example that denies all agents across an organization the ability to create or delete buckets. That is the kind of ceiling the checklist asks for (check), and it sits above any role granted to a single agent (check). Google documents agent identity as tied to the lifecycle of the agent (check). A service account is a separate resource, so retiring the agent leaves the account and its grants in place until someone deletes them. Limit who can attach a service account to a resource by granting the Service Account User role narrowly (check). Google documents that the Service Account User role lets a principal attach a service account to a resource, which gives the resource's workloads that account's access.

Gemini Enterprise registers agents that run here

Agents registered in Gemini Enterprise run on Agent Runtime, so the identity above applies to them. Google documents that registering an ADK agent requires the Gemini Enterprise Admin role for the person doing it, and that Gemini Enterprise gives ADK agents the user's email address. An agent that must reach Google Cloud resources on a user's behalf needs authorization details set up: an OAuth client, an authorization resource registered with Gemini Enterprise, and user consent. A Gemini Enterprise administrator can see the agent's identity, typically its SPIFFE ID. Permissions that Gemini Enterprise itself grants a registered agent were none found on 2026-11-10 in the pages read. Read it with the Agent Runtime pages to get the full reach of a registered agent.

Network access needs its own decision

The identity says what the agent may call. The network says where the call can go. Google documents that the agent runs in a Google-managed network with no access to your VPC unless you configure a Private Service Connect interface. The interface needs the Agent Platform Service Agent of the host project to hold either the Compute Network Admin role or a custom role with listed permissions, which is itself a grant to review. With VPC Service Controls, the interface is required for internet access. The network guide covers the rest, and the checklist has the 30 checks.

Sources

  1. Google Cloud: agent identity on Agent Runtime, read 10 Nov 2026
  2. Google Cloud: set up Agent Runtime, read 10 Nov 2026
  3. Google Cloud: types of service accounts and service agents, read 10 Nov 2026
  4. Google Cloud: Private Service Connect interface with Agent Runtime, read 10 Nov 2026
  5. Google Cloud: service account permissions, read 10 Nov 2026

Last reviewed 16 Nov 2026.