Create a new Metabase dashboard - use this to build new analytical views, organize related cards, or establish monitoring interfaces
AI agents use create_dashboard to create or update resources in Metabase MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Metabase MCP Server environment.
Creating a dashboard is a Write operation because it produces new data structures within Metabase that can be subsequently modified or deleted. It has no financial impact, does not execute arbitrary code, and is fully reversible.
From the tool's definition Tool description states 'Create a new Metabase dashboard' - the verb 'create' indicates a write operation that adds new data/objects to the system. The description emphasizes building and organizing analytical views, which are reversible modifications.
Attacks that exploit this kind of access
Create a new Metabase dashboard - use this to build new analytical views, organize related cards, or establish monitoring interfaces. It is categorised as a Write tool in the Metabase MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Metabase MCP 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 MCP Server. Nothing to install.
create_dashboard is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
create_dashboard is provided by the Metabase MCP Server MCP server (thangnm93/metabase-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →