bigquery_load_csv_data
AI agents use bigquery_load_csv_data 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.
The tool name strongly suggests loading (writing) CSV data into BigQuery, which is a Write operation. The description is empty, reducing confidence. Given sibling tools like bigquery_export_table and bigquery_run_query, this tool likely creates or appends data to a BigQuery table. Severity is high because bulk loading could overwrite or significantly alter large datasets, and misuse could corrupt important data.
From the tool's definition Tool name 'bigquery_load_csv_data' — 'load_csv_data' implies importing/writing CSV data into BigQuery.
Attacks that exploit this kind of access
bigquery_load_csv_data. 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_load_csv_data: 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_load_csv_data 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_load_csv_data 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_load_csv_data. 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_load_csv_data 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 →