create_card · Metabase MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_card does on Metabase MCP Server

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

WHY IT NEEDS A POLICY

Why create_card needs a policy

This tool creates new persistent analytics objects (Metabase cards) in the system. While this modifies the state of the Metabase instance by adding new cards, the operation is reversible (cards can be deleted). It does not execute arbitrary code, delete data, or move funds. The blast radius is bounded to analytics metadata rather than core data, making it Write rather than Execute.

From the tool's definition Tool description explicitly states 'Create a new Metabase card' and 'programmatically build new analytical cards, dashboards charts'. The verb 'Create' and the action of building new analytics objects demonstrates data creation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_card Rate-limited

create_card 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_card": {
      "limits": [
        {
          "counter": "create_card_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Metabase MCP Server, so you can run agents against it safely.

FAQ

Questions about create_card

What does the create_card tool do? +

Create a new Metabase card with custom query, visualization type, and settings - use this to programmatically build new analytical cards, dashboards charts, or data exploration queries. 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.

How do I enforce a policy on create_card? +

Register the Metabase MCP Server MCP server in PolicyLayer and add a rule for create_card: 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.

What risk level is create_card? +

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

Can I rate-limit create_card? +

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

Set action: deny in the PolicyLayer policy for create_card. 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_card? +

create_card 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.