gcp_bq_run_query
Run a BigQuery SQL query
This record as markdown: /tools/ahmedselimmansor-ctrl-gcp-mcp-server/gcp-bq-run-query.md
What gcp_bq_run_query does on GCP MCP Server
AI agents invoke gcp_bq_run_query to trigger actions in GCP MCP Server. 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 gcp_bq_run_query is rated High
This tool executes SQL queries against BigQuery, which qualifies as Execute since it triggers external operations (SQL execution) whose effects depend entirely on the query argument provided by the user.
From the tool's definition Tool name 'gcp_bq_run_query' and description 'Run a BigQuery SQL query' indicate execution of arbitrary SQL queries. BigQuery is a data warehouse where SQL queries can read, modify, or delete data depending on query content.
Attacks that exploit this kind of access
The rule that runs gcp_bq_run_query safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GCP MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gcp_bq_run_query, this is the rule to start with:
gcp_bq_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.
The button opens the PolicyLayer dashboard: create your workspace, connect GCP MCP Server, apply this rule, and every gcp_bq_run_query call is checked against it from then on.
Questions about gcp_bq_run_query
Run a BigQuery SQL query. It is categorised as a Execute tool in the GCP MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the GCP MCP Server MCP server in PolicyLayer and add a rule for gcp_bq_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 GCP MCP Server. Nothing to install.
gcp_bq_run_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the gcp_bq_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.
Set action: deny in the PolicyLayer policy for gcp_bq_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.
gcp_bq_run_query is provided by the GCP MCP Server MCP server (ahmedselimmansor-ctrl/gcp_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GCP MCP Server, and thousands of servers like it.
Across the catalogue