gcp_bq_delete_table
Delete a BigQuery table
This record as markdown: /tools/ahmedselimmansor-ctrl-gcp-mcp-server/gcp-bq-delete-table.md
What gcp_bq_delete_table does on GCP MCP Server
AI agents call gcp_bq_delete_table to permanently remove resources in GCP MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why gcp_bq_delete_table is rated Critical
Deleting a BigQuery table permanently removes data and cannot be undone (barring restore from backups, which are not guaranteed). This is a classic destructive operation with potentially severe impact depending on the table's size, criticality, and whether backups exist. High severity reflects the potential for significant data loss; confidence is very high due to unambiguous naming and description.
From the tool's definition Tool name 'gcp_bq_delete_table' and description 'Delete a BigQuery table' explicitly indicate permanent deletion of data. The verb 'delete' and the irreversible nature of removing a table constitute a destructive operation.
Attacks that exploit this kind of access
The rule that runs gcp_bq_delete_table 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_delete_table, this is the rule to start with:
gcp_bq_delete_table is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect GCP MCP Server, apply this rule, and every gcp_bq_delete_table call is checked against it from then on.
Questions about gcp_bq_delete_table
Delete a BigQuery table. It is categorised as a Destructive tool in the GCP MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GCP MCP Server MCP server in PolicyLayer and add a rule for gcp_bq_delete_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 GCP MCP Server. Nothing to install.
gcp_bq_delete_table is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the gcp_bq_delete_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 gcp_bq_delete_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.
gcp_bq_delete_table 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