bigquery_export_table
AI agents call bigquery_export_table 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.
The name implies reading/exporting data from BigQuery, which is a Read operation. However, exporting could also involve writing to a destination (e.g., Cloud Storage), making it potentially a Write. With no description available, confidence is low. Choosing Read as the base interpretation of 'export' (retrieving/outputting data), but severity is medium because exporting could expose sensitive data at scale.
From the tool's definition Tool name 'bigquery_export_table' suggests exporting/reading data from a BigQuery table; description is empty and uninformative.
Attacks that exploit this kind of access
bigquery_export_table. 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_export_table: 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_export_table 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_export_table 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_export_table. 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_export_table 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 →