Create a new BigQuery dataset
AI agents use bigquery_create_dataset to create or update resources in Google Cloud — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Cloud environment.
This tool creates a new BigQuery dataset, which is a write operation that modifies the data infrastructure. While reversible (datasets can be deleted), it can impact multiple downstream processes, applications, and analytical pipelines that may depend on dataset naming conventions and structures.
From the tool's definition Tool name 'bigquery_create_dataset' and description 'Create a new BigQuery dataset' indicate creation of a new dataset, which is a reversible data structure modification.
Attacks that exploit this kind of access
Create a new BigQuery dataset. It is categorised as a Write tool in the Google Cloud MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Cloud MCP server in PolicyLayer and add a rule for bigquery_create_dataset: 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_create_dataset is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the bigquery_create_dataset 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_create_dataset. 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_create_dataset 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 →