update_dashboard

Update an existing dashboard

SERVERMetabase MCP SOURCE1luvc0d3/metabase-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/1luvc0d3-metabase-mcp/update-dashboard.md

WHAT IT DOES

What update_dashboard does on Metabase MCP

AI agents use update_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.

RISK

Why update_dashboard is rated Medium

The tool modifies existing dashboard data (title, layout, cards, filters, etc.) but does not delete resources or execute arbitrary queries. Changes are reversible through subsequent updates.

From the tool's definition Tool name 'update_dashboard' and description 'Update an existing dashboard' indicate modification of dashboard configuration or content. This is a reversible change operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_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 update_dashboard, this is the rule to start with:

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.

The button opens the PolicyLayer dashboard: create your workspace, connect Metabase MCP, apply this rule, and every update_dashboard call is checked against it from then on.

FAQ

Questions about update_dashboard

What does the update_dashboard tool do? +

Update an existing 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.

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 MCP. 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 (1luvc0d3/metabase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Metabase, and thousands of servers like it.

This server

All 30 Metabase tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →