create_collection · Metabase MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_collection does on Metabase MCP Server

AI agents use create_collection 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_collection needs a policy

This tool creates new metadata/organizational structures within Metabase (collections). The action is reversible—collections can be deleted or modified after creation—so it does not meet the Destructive threshold. It does not execute arbitrary code, query databases, or involve financial transactions. Creating collections is a Write operation as it modifies the Metabase environment state.

From the tool's definition create_collection directly creates a new Metabase collection, which is a reversible data modification operation. The description uses the verb 'Create' and explicitly states the tool will 'establish organizational containers' for analytical content.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_collection Rate-limited

create_collection 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_collection": {
      "limits": [
        {
          "counter": "create_collection_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_collection

What does the create_collection tool do? +

Create a new Metabase collection for organizing analytical content - use this to establish organizational containers for cards, dashboards, and reports. 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_collection? +

Register the Metabase MCP Server MCP server in PolicyLayer and add a rule for create_collection: 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_collection? +

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

Can I rate-limit create_collection? +

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

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

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