Remove a card from a dashboard.
AI agents call remove_card_from_dashboard 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.
Removing a card from a dashboard detaches it permanently; there is no indication of an undo/restore mechanism, making this a destructive operation. High severity because it can eliminate visualizations and data from dashboards that may be shared across an organization.
From the tool's definition "Remove a card from a dashboard" — the word 'remove' indicates an irreversible deletion of the card-dashboard association
Attacks that exploit this kind of access
Remove a card from a dashboard. 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 remove_card_from_dashboard: 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.
remove_card_from_dashboard 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 remove_card_from_dashboard 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 remove_card_from_dashboard. 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.
remove_card_from_dashboard 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 →