Delete a card (saved question).
AI agents call delete_card to permanently remove resources in Metabase Mcp Navi — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a saved question (card) from Metabase. Deletion is an irreversible operation that destroys data and cannot be undone without administrative recovery measures. This places it in the Destructive category (more severe than Write, which covers reversible modifications). Severity is high because a Metabase card may represent significant analytical work and business context.
From the tool's definition Tool name: delete_card. Description: 'Delete a card (saved question).' The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a card (saved question). It is categorised as a Destructive tool in the Metabase Mcp Navi MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Metabase Mcp Navi 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 Navi. 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 Navi MCP server (manish-coder-1007/metabase-mcp-navi). 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 →