add_card_to_dashboard
Add a card/question to a dashboard
This record as markdown: /tools/1luvc0d3-metabase-mcp/add-card-to-dashboard.md
What add_card_to_dashboard does on Metabase MCP
AI agents use add_card_to_dashboard to create or update resources in Metabase MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Metabase MCP environment.
Why add_card_to_dashboard is rated Medium
This tool creates an association between a card and dashboard, changing the dashboard's composition. It is Write rather than Read (it modifies state), and not Destructive (the change is reversible—the card can be removed). The blast radius is medium because misconfiguration could clutter dashboards or expose unintended data views, but the operation is not irreversible and does not execute external code or move money.
From the tool's definition Tool description states 'Add a card/question to a dashboard' — this modifies dashboard state by inserting a new element, a reversible write operation.
Attacks that exploit this kind of access
The rule that runs add_card_to_dashboard safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Metabase MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_card_to_dashboard, this is the rule to start with:
add_card_to_dashboard stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Metabase MCP, apply this rule, and every add_card_to_dashboard call is checked against it from then on.
Questions about add_card_to_dashboard
Add a card/question to a dashboard. It is categorised as a Write tool in the Metabase MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Metabase MCP server in PolicyLayer and add a rule for add_card_to_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.
add_card_to_dashboard is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_card_to_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 add_card_to_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.
add_card_to_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.
This server
Across the catalogue