update_dashboard

Update an existing dashboard

SERVERMetabase Analytics Integration Server SOURCEzsh52013148087/metabase-mcp

Medium RISK CLASS

Category Write

Parameters 110 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What update_dashboard does on Metabase Analytics Integration Server

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

Parameter	Type	Required	Description
`name`	string	—	New name for the dashboard
`archived`	boolean	—	Whether to archive the dashboard
`cache_ttl`	number	—	Cache time-to-live in seconds
`parameters`	array	—	Updated dashboard filter parameters
`description`	string	—	New description for the dashboard
`dashboard_id`	number	—	ID of the dashboard to update
`collection_id`	number	—	New collection ID for the dashboard
`embedding_params`	object	—	Parameters configuration for embedding
`enable_embedding`	boolean	—	Whether to enable embedding
`auto_apply_filters`	boolean	—	Whether filters should auto-apply
`collection_position`	number	—	New position within the collection

Parameters from the server's own tool schema.

RISK

Why update_dashboard is rated Medium

Updating a dashboard alters stored configuration, metadata, or layout settings but does not delete data or execute external operations. This is a classic Write operation: reversible modification of data. Severity is medium because unauthorized dashboard updates could mislead analysts or disrupt analytics workflows, but the changes can be reverted and no data is destroyed or financial impact occurs.

From the tool's definition Tool name is 'update_dashboard' and description states 'Update an existing dashboard' — this modifies existing data (dashboard configuration) reversibly.

Risk signalsHigh parameter count (11 properties)

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 Analytics Integration Server, 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 Analytics Integration Server, 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 Analytics Integration Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does update_dashboard accept? +

update_dashboard accepts 11 parameters: name, archived, cache_ttl, parameters, description, dashboard_id, collection_id, embedding_params, enable_embedding, auto_apply_filters, collection_position. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_dashboard? +

Register the Metabase Analytics Integration Server 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 Analytics Integration Server. 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 Analytics Integration Server MCP server (zsh52013148087/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 Analytics Integration Server, and thousands of servers like it.

This server

All 16 Metabase Analytics Integration Server tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

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