Permanently delete a Metabase collection - use with caution as this affects contained content and cannot be undone
AI agents call delete_collection 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 permanently and irreversibly deletes a Metabase collection along with all its contained dashboards, cards, and other content. The description explicitly warns this 'cannot be undone', placing it squarely in the Destructive category (irreversibly deletes data).
From the tool's definition "Permanently delete a Metabase collection" and "cannot be undone" - explicitly indicates irreversible deletion of data and contained content
Attacks that exploit this kind of access
Permanently delete a Metabase collection - use with caution as this affects contained content and cannot be undone. 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 delete_collection: 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.
delete_collection 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 delete_collection 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 delete_collection. 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.
delete_collection 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 →