create_card
Create a new question/card in Metabase
This record as markdown: /tools/zsh52013148087-metabase-mcp/create-card.md
What create_card does on Metabase Analytics Integration Server
AI agents use create_card 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 card |
query | string | — | SQL query for the card |
database_id | number | — | ID of the database to query |
description | string | — | Description of the card |
viz_settings | object | — | Visualization settings for the card |
collection_id | number | — | ID of the collection to put the card in (optional) |
collection_position | number | — | Position within the collection (optional) |
Parameters from the server's own tool schema.
Why create_card is rated Medium
Creating a card/question is a data modification action that is reversible (the card can be deleted or modified later). It does not execute queries, delete data, move money, or trigger external operations. This places it in the Write category.
From the tool's definition Tool is described as 'Create a new question/card in Metabase', which performs a reversible creation operation that adds a new artifact to the analytics platform without deleting or executing external commands.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
The rule that runs create_card 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_card, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Metabase Analytics Integration Server, apply this rule, and every create_card call is checked against it from then on.
Questions about create_card
Create a new question/card 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_card accepts 7 parameters: name, query, database_id, description, viz_settings, collection_id, collection_position. 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_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 Analytics Integration Server. Nothing to install.
create_card 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_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.
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.
create_card 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