Remove a Metabase card either by archiving (soft delete, preserves history) or permanent deletion - use this to clean up unused cards, remove broken cards, or organize analytical content
AI agents call delete_card 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 deletes data (Metabase cards/queries) from the analytics platform. While it offers a soft-delete (archiving) option, it also permits permanent deletion which cannot be undone. This makes it Destructive rather than Write.
From the tool's definition Tool name is 'delete_card' and description explicitly states 'permanent deletion' alongside archiving option. The description indicates irreversible removal of analytical content.
Attacks that exploit this kind of access
Remove a Metabase card either by archiving (soft delete, preserves history) or permanent deletion - use this to clean up unused cards, remove broken cards, or organize analytical content. 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_card: 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_card 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_card 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_card. 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_card 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 →