Completely replace table data with new CSV content - use this for full data refreshes, model updates, or complete table replacements
AI agents call replace_table_csv to permanently remove resources in Metabase MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly destroys all existing table data by replacing it wholesale with new CSV content. There is no indication of a backup or undo mechanism. Misuse by an AI agent could wipe entire production tables, making this a critical destructive operation.
From the tool's definition 'Completely replace table data with new CSV content' and 'complete table replacements' — existing data is entirely overwritten and cannot be recovered
Attacks that exploit this kind of access
Completely replace table data with new CSV content - use this for full data refreshes, model updates, or complete table replacements. It is categorised as a Destructive tool in the Metabase MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Metabase MCP Server MCP server in PolicyLayer and add a rule for replace_table_csv: 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 Metabase MCP Server. Nothing to install.
replace_table_csv 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 replace_table_csv 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 replace_table_csv. 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.
replace_table_csv is provided by the Metabase MCP Server MCP server (thangnm93/metabase-mcp-server). 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 →