New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

remove_card_from_dashboard

Remove a card from a dashboard

SERVERMetabase MCP SOURCE1luvc0d3/metabase-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/1luvc0d3-metabase-mcp/remove-card-from-dashboard.md

What remove_card_from_dashboard does on Metabase MCP

AI agents call remove_card_from_dashboard to permanently remove resources in Metabase MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why remove_card_from_dashboard is rated Critical

Removing a card from a dashboard destroys the dashboard-card relationship. While the card itself may still exist, the layout/configuration of the dashboard is permanently altered and the removal cannot be undone without manually re-adding and reconfiguring the card. This qualifies as Destructive. The blast radius is high because dashboards are shared resources used by multiple stakeholders.

From the tool's definition 'Remove a card from a dashboard' — removing a card from a dashboard is an irreversible deletion of the association between the card and the dashboard

Questions about remove_card_from_dashboard

What does the remove_card_from_dashboard tool do? +

Remove a card from a dashboard. It is categorised as a Destructive tool in the Metabase MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_card_from_dashboard? +

Register the Metabase 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. Nothing to install.

What risk level is remove_card_from_dashboard? +

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.

Can I rate-limit remove_card_from_dashboard? +

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.

How do I block remove_card_from_dashboard completely? +

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.

What MCP server provides remove_card_from_dashboard? +

remove_card_from_dashboard is provided by the Metabase MCP server (1luvc0d3/metabase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Metabase, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Metabase's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.