This record as markdown: /tools/1luvc0d3-metabase-mcp/create-collection.md
What create_collection does on Metabase MCP
AI agents use create_collection to create or update resources in Metabase MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Metabase MCP environment.
Why create_collection is rated Medium
This tool creates a new collection (a data structure) in Metabase but does not execute queries, delete data, or move financial resources. While collections can organize cards and dashboards, the action itself is reversible (collections can be deleted).
From the tool's definition Tool name 'create_collection' and description 'Create a new collection' indicate creation of a new organizational/data container within Metabase, which is a reversible write operation.
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 MCP, 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 MCP, apply this rule, and every create_collection call is checked against it from then on.
Questions about create_collection
Create a new collection. It is categorised as a Write tool in the Metabase MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Metabase 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. 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 MCP server (1luvc0d3/metabase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Metabase, and thousands of servers like it.
This server
Across the catalogue