create_collection
Create a new collection in Metabase
This record as markdown: /tools/zsh52013148087-metabase-mcp/create-collection.md
What create_collection does on Metabase Analytics Integration Server
AI agents use create_collection 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 collection |
color | string | — | Color for the collection (optional) |
parent_id | number | — | ID of the parent collection (optional) |
description | string | — | Description of the collection |
Parameters from the server's own tool schema.
Why create_collection is rated Medium
Creating a collection is a write operation that adds a new resource to Metabase. It modifies the platform state by introducing a new collection structure that can organize cards and dashboards, but the operation is reversible (collections can be deleted). This is not destructive since it doesn't delete data.
From the tool's definition Tool name is 'create_collection' and description states 'Create a new collection in Metabase' — this creates a new organizational container/resource in the analytics platform.
Attacks that exploit this kind of access
The rule that runs create_collection 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_collection, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Metabase Analytics Integration Server, apply this rule, and every create_collection call is checked against it from then on.
Questions about create_collection
Create a new collection 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.
create_collection accepts 4 parameters: name, color, parent_id, description. The full parameter table on this page comes from the server's own tool schema.
Register the Metabase Analytics Integration 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 Analytics Integration Server. Nothing to install.
create_collection 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_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.
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.
create_collection 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.
More on Metabase Analytics Integration Server, and thousands of servers like it.
Across the catalogue