# update_dashboard

Update an existing dashboard

Agent View of the PolicyLayer registry record for `update_dashboard`. HTML page: https://policylayer.com/tools/zsh52013148087-metabase-mcp/update-dashboard

## Facts

- Tool: `update_dashboard`
- Server: Metabase Analytics Integration Server (`zsh52013148087/metabase-mcp`) — https://policylayer.com/tools/zsh52013148087-metabase-mcp.md
- Homepage: https://github.com/zsh52013148087/metabase-mcp
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 11
- Recommended policy verdict: Rate-limited

## Parameters

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

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "update_dashboard",
    "arguments": {}
  }
}
```

## 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 own definition: "Tool name is 'update_dashboard' and description states 'Update an existing dashboard' — this modifies existing data (dashboard configuration) reversibly."

Risk signals: High parameter count (11 properties)

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Metabase Analytics Integration Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_dashboard": {
      "limits": [
        {
          "counter": "update_dashboard_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Metabase Analytics Integration Server (15)

- `delete_dashboard` — Destructive — https://policylayer.com/tools/zsh52013148087-metabase-mcp/delete-dashboard.md
- `execute_card` — Execute — https://policylayer.com/tools/zsh52013148087-metabase-mcp/execute-card.md
- `execute_query` — Execute — https://policylayer.com/tools/zsh52013148087-metabase-mcp/execute-query.md
- `get_dashboard_cards` — Read — https://policylayer.com/tools/zsh52013148087-metabase-mcp/get-dashboard-cards.md
- `get_table_fields` — Read — https://policylayer.com/tools/zsh52013148087-metabase-mcp/get-table-fields.md
- `list_cards` — Read — https://policylayer.com/tools/zsh52013148087-metabase-mcp/list-cards.md
- `list_collections` — Read — https://policylayer.com/tools/zsh52013148087-metabase-mcp/list-collections.md
- `list_dashboards` — Read — https://policylayer.com/tools/zsh52013148087-metabase-mcp/list-dashboards.md
- `list_databases` — Read — https://policylayer.com/tools/zsh52013148087-metabase-mcp/list-databases.md
- `list_tables` — Read — https://policylayer.com/tools/zsh52013148087-metabase-mcp/list-tables.md
- `add_card_to_dashboard` — Write — https://policylayer.com/tools/zsh52013148087-metabase-mcp/add-card-to-dashboard.md
- `create_card` — Write — https://policylayer.com/tools/zsh52013148087-metabase-mcp/create-card.md
- `create_collection` — Write — https://policylayer.com/tools/zsh52013148087-metabase-mcp/create-collection.md
- `create_dashboard` — Write — https://policylayer.com/tools/zsh52013148087-metabase-mcp/create-dashboard.md
- `update_card_visualization` — Write — https://policylayer.com/tools/zsh52013148087-metabase-mcp/update-card-visualization.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=zsh52013148087-metabase-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/zsh52013148087-metabase-mcp