Permanently remove a database from Metabase - use with caution as this will break dependent content and cannot be undone
AI agents call delete_database 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 infrastructure (an entire database) from the system. The description emphasizes it 'cannot be undone' and will 'break dependent content', indicating cascading destructive effects. An AI agent misusing this could cause severe operational damage by removing critical analytics infrastructure and all dependent dashboards/cards.
From the tool's definition Tool description explicitly states 'Permanently remove a database from Metabase' and warns 'cannot be undone'. The verb 'delete' combined with 'permanently' and irreversibility confirms destructive classification.
Attacks that exploit this kind of access
Permanently remove a database from Metabase - use with caution as this will break dependent 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_database: 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_database 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_database 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_database. 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_database 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 →