bigquery_run_query · Google Cloud MCP: Risk & Policy

WHAT IT DOES

What bigquery_run_query does on Google Cloud

AI agents invoke bigquery_run_query to trigger actions in Google Cloud. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why bigquery_run_query needs a policy

This tool executes code (SQL) whose effects depend entirely on the query argument supplied by the agent. While it may primarily perform reads, SQL execution can modify data, trigger stored procedures, or access sensitive information. Without restrictions on query content, an agent could execute DELETE, UPDATE, or DROP statements.

From the tool's definition Tool name 'bigquery_run_query' and description 'Execute a BigQuery SQL query' explicitly indicate execution of arbitrary SQL queries against BigQuery.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bigquery_run_query Rate-limited

bigquery_run_query stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bigquery_run_query": {
      "limits": [
        {
          "counter": "bigquery_run_query_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Google Cloud, so you can run agents against it safely.

FAQ

Questions about bigquery_run_query

What does the bigquery_run_query tool do? +

Execute a BigQuery SQL query. It is categorised as a Execute tool in the Google Cloud MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on bigquery_run_query? +

Register the Google Cloud MCP server in PolicyLayer and add a rule for bigquery_run_query: 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.

What risk level is bigquery_run_query? +

bigquery_run_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit bigquery_run_query? +

Yes. Add a rate_limit block to the bigquery_run_query 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.

How do I block bigquery_run_query completely? +

Set action: deny in the PolicyLayer policy for bigquery_run_query. 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.

What MCP server provides bigquery_run_query? +

bigquery_run_query 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.