Skip to main content
Integrations · Google Compute
A Guild agent can list, start, stop, and otherwise manage Compute Engine instances, disks, images, networks, and more on your behalf. Guild stores the OAuth service account credential server-side and injects it into every request, so agent code never sees it. Credential policies let you restrict exactly which operations and resources each agent can reach, and every call is recorded in Guild’s audit trail.

Book a demo

See how teams govern agents that use Google Compute.

Talk to sales

Get access to Guild, then connect Google Compute to your first agent.

What the Google Compute integration exposes

The integration provides tools covering Compute Engine instances, persistent disks, machine images, snapshots, networks, subnetworks, instance templates, machine types, zones, regions, and long-running operations. Instance tools let agents get, insert, delete, start, stop, suspend, resume, reset, and update VMs, as well as attach and detach disks, read serial port output, and capture screenshots. Disk tools cover create, resize, update, and delete. Operation tools let agents poll or wait on both global and zone-scoped async operations.

How it works

1

Open Credentials in Guild

Go to Access & setup > Credentials in your Guild account or organization. Admins manage organization-level credentials; members can connect credentials scoped to themselves.
2

Authorize Google Compute

Click Google Compute and complete the OAuth flow with a Google account that has Compute Engine permissions. Guild refreshes the token automatically.
3

Add tools to your agent

Import googleComputeTools and spread it into your agent’s tools object. Use pick to include only the tools your agent needs, referencing tool names by their google_compute_ prefix.

Why Google Compute access needs governing

Guild’s credential proxy enforces credential policies before any request leaves the platform. You write ALLOW and DENY rules that match by operation name, supporting glob patterns such as google_compute_instances_delete or google_compute_instances_* so you can block destructive calls while permitting read-only ones. Rules can be scoped to specific agents or workspaces, letting one agent list instances while another manages disks, all on a single connected credential. The credential itself never enters agent code, the container, or the prompt. Guild injects it server-side only after the policy check passes, as described in the security architecture. You can scope a credential to one workspace, one member, or a single agent using the credentials page, and restrict a workspace to its own credentials so shared organization credentials cannot be used there. Agents with no matching allow rule are denied by default once you delete the auto-created allow-all policy.

About the Google Compute integration

The @guildai-services/guildai~google-compute package gives your agents access to Google Cloud compute resources through Guild’s Google Compute integration.

Authentication

  • Type: OAuth 2.0 (service account)
  • Token management: Refreshed automatically by Guild

Setup

1

Open Credentials

Go to Credentials in Guild.
2

Connect Google Compute

Click Google Compute and authorize with a Google account that has Compute permissions.

Usage

Selecting specific tools

Tools are named with the google_compute_ prefix. Use pick() to include only what your agent needs.

Tools

Tools in the latest published version of guildai~google-compute:

Frequently asked questions

Yes. Write a credential policy with a DENY rule targeting google_compute_instances_stop and google_compute_instances_delete, then an ALLOW rule for google_compute_instances_* to permit the rest. DENY rules always take precedence over ALLOW rules, so the destructive operations stay blocked even if a wildcard allow matches them.
No. The catalog entry for this integration lists no webhook events, so agents cannot subscribe to Compute Engine event notifications through Guild.
Guild refreshes the OAuth service account token automatically. The token is stored server-side and added to outbound requests by Guild’s credential proxy. Agent code never sees it.
Yes. You can connect a credential dedicated to a single agent from the installed agent’s page, or grant an existing member credential to a specific agent. Guild resolves credentials in a defined order, checking agent-level grants and dedicated credentials before workspace or account defaults, so each agent can authenticate as a different Google account.

Put a governed agent on Google Compute this week

Book a demo

See how teams govern agents that use Google Compute.

Talk to sales

Get access to Guild, then connect Google Compute to your first agent.
Also runs on Guild: Azure DevOps · Bitbucket · GitHub · Linear Read: Docs: Credential policies · Credentials · Tools in agents
Last modified on November 4, 2026