add_card_to_dashboard · Metabase Mcp Navi MCP: Risk & Policy

WHAT IT DOES

What add_card_to_dashboard does on Metabase Mcp Navi

AI agents use add_card_to_dashboard to create or update resources in Metabase Mcp Navi — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Metabase Mcp Navi environment.

WHY IT NEEDS A POLICY

Why add_card_to_dashboard needs a policy

This tool creates or modifies dashboard structure by adding cards to dashboards. While reversible (cards can be removed), it changes dashboard state and composition. It falls under Write category rather than Read (it modifies state), Execute (it doesn't run arbitrary operations), or Destructive (it's reversible). The empty description reduces confidence slightly, but the name clearly indicates a modification action.

From the tool's definition Tool name 'add_card_to_dashboard' indicates a modification operation that adds a card (visualization) to a dashboard. This is a create/modify action on dashboard composition.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_card_to_dashboard Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_card_to_dashboard": {
      "limits": [
        {
          "counter": "add_card_to_dashboard_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Metabase Mcp Navi, so you can run agents against it safely.

FAQ

Questions about add_card_to_dashboard

What does the add_card_to_dashboard tool do? +

add_card_to_dashboard. It is categorised as a Write tool in the Metabase Mcp Navi MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_card_to_dashboard? +

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

What risk level is add_card_to_dashboard? +

add_card_to_dashboard is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_card_to_dashboard? +

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.

How do I block add_card_to_dashboard completely? +

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.

What MCP server provides add_card_to_dashboard? +

add_card_to_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.