List all BigQuery datasets in the project
AI agents call bigquery_list_datasets to retrieve information from Google Cloud without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query/list operation to retrieve metadata about existing BigQuery datasets. It is read-only with no capability to modify, delete, or execute operations. The blast radius of misuse is minimal—an agent could only enumerate datasets, which represents information disclosure risk. Low severity because dataset names alone are typically not sensitive, though they may reveal organizational structure.
From the tool's definition Tool name 'bigquery_list_datasets' and description 'List all BigQuery datasets in the project' indicate a retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
List all BigQuery datasets in the project. It is categorised as a Read tool in the Google Cloud MCP Server, which means it retrieves data without modifying state.
Register the Google Cloud MCP server in PolicyLayer and add a rule for bigquery_list_datasets: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Google Cloud. Nothing to install.
bigquery_list_datasets is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the bigquery_list_datasets rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for bigquery_list_datasets. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
bigquery_list_datasets is provided by the Google Cloud MCP server (lockon-n/google-cloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →