create_dashboard

Create a new dashboard in Metabase

SERVERMetabase Analytics Integration Server SOURCEzsh52013148087/metabase-mcp

Medium RISK CLASS

Category Write

Parameters 80 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What create_dashboard does on Metabase Analytics Integration Server

AI agents use create_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	—	Name of the dashboard
`cache_ttl`	number	—	Cache time-to-live in seconds
`parameters`	array	—	Dashboard filter parameters (optional)
`description`	string	—	Description of the dashboard
`collection_id`	number	—	ID of the collection to put the dashboard in (optional)
`enable_embedding`	boolean	—	Whether to enable embedding for this dashboard
`auto_apply_filters`	boolean	—	Whether filters should auto-apply
`collection_position`	number	—	Position within the collection (optional)

Parameters from the server's own tool schema.

RISK

Why create_dashboard is rated Medium

This tool creates a new dashboard, which is a reversible write operation. It modifies the state of the Metabase system by adding a new dashboard, but does not delete or execute arbitrary code. The blast radius is medium because a malicious agent could create many dashboards consuming resources or causing confusion, but the action can be undone by deleting the created dashboard.

From the tool's definition Tool name is 'create_dashboard' and description states 'Create a new dashboard in Metabase', which creates new data/objects in the analytics platform.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

create_dashboard Rate-limited

create_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": {
    "create_dashboard": {
      "limits": [
        {
          "counter": "create_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 create_dashboard call is checked against it from then on.

FAQ

Questions about create_dashboard

What does the create_dashboard tool do? +

Create a new dashboard in Metabase. 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 create_dashboard accept? +

create_dashboard accepts 8 parameters: name, cache_ttl, parameters, description, collection_id, 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 create_dashboard? +

Register the Metabase Analytics Integration Server MCP server in PolicyLayer and add a rule for create_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 create_dashboard? +

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

Can I rate-limit create_dashboard? +

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

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

create_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

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

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