Agent skill · google

agent-platform-access-audit

Audits AI agent data access, blast radius, and blocked policy operations in Google Cloud by querying Cloud Audit Logs via BigQuery. Use when investigating what resources or services an agent accessed, identifying top originating principals the agent is acting as, or triaging PERMISSION_DENIED errors to distinguish VPC Service Controls perimeter violations from IAM permission denials. Don't use for configuring Cloud Monitoring alert policies, modifying IAM policies or VPC Service Controls perimeters, querying non-audit application logs, or performing write operations.

What it needs

About 6k tokens when loaded.

What this skill does

Agent Access Audit Use this skill to audit AI agent resource accesses, blast radius, and policy denials in Google Cloud using Cloud Audit Logs. Usage Attribution MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read and follow the instructions in Usage Attribution. Prerequisites Only refer to this section if a command fails. Proceed directly with the workflow below, and only if a gcloud or bq command fails with an authentication, API, billing, or PERMISSIONDENIED error, tell the user what they need to do (do NOT configure or grant these yourself): Google Cloud CLI: gcloud and bq installed (installation guide). Authentication: Active credentials via gcloud auth login or gcloud auth application-default login. Active Billing Account: The Google Cloud project must have an active billing account attached (required for running bq query jobs against AllLogs). Enabled APIs: logging.googleapis.com, bigquery.googleapis.com, and agentregistry.googleapis.com. If any required API is disabled, provide the exact enablement command: IAM roles on the project: roles/logging.privateLogViewer, roles/bigquery.dataViewer, roles/bigquery.jobUser, and roles/agentregistry.viewer. -------------------------------------------------------------------------------- Execution workflow Follow these steps in order before answering any audit question: Step 1: Resolve the project ID ({PROJECTID}) 1. If the user explicitly provides a Google Cloud project ID in the prompt, use that project ID. 2. If the project ID is omitted from the prompt, run: 3. If gcloud config get-value project returns empty or (unset), stop and ask the user which Google Cloud project ID to query. Never leave {PROJECTID} as a literal placeholder in a SQL query. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills google/agent-platform-access-audit

View the source on GitHub

Browse the @skills marketplace