update_dashboard · Metabase MCP: Risk & Policy

WHAT IT DOES

What update_dashboard does on Metabase

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

WHY IT NEEDS A POLICY

Why update_dashboard needs a policy

The name 'update_dashboard' indicates modification of an existing dashboard resource. This is a reversible write operation (configuration can be changed again), not destructive (dashboards remain) or execute (no code execution implied). Despite the empty description, the naming convention and server context (Metabase dashboard management) strongly indicate data modification capability.

From the tool's definition Tool name 'update_dashboard' combined with sibling tools that include 'create_dashboard', 'create_card', and 'add_card_to_dashboard' establish this server's pattern of write operations. The tool modifies dashboard configuration/state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_dashboard Rate-limited

update_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": {
    "update_dashboard": {
      "limits": [
        {
          "counter": "update_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, so you can run agents against it safely.

FAQ

Questions about update_dashboard

What does the update_dashboard tool do? +

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

How do I enforce a policy on update_dashboard? +

Register the Metabase MCP server in PolicyLayer and add a rule for update_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. Nothing to install.

What risk level is update_dashboard? +

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

Can I rate-limit update_dashboard? +

Yes. Add a rate_limit block to the update_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 update_dashboard completely? +

Set action: deny in the PolicyLayer policy for update_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 update_dashboard? +

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