This record as markdown: /tools/1luvc0d3-metabase-mcp/create-card.md
What create_card does on Metabase MCP
AI agents use create_card 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_card is rated Medium
This tool creates new persistent objects (cards/questions) in Metabase. It is a Write operation because it creates reversible data structures that can be subsequently modified or deleted. Severity is medium because while the creation of analytics cards has manageable blast radius (they can be deleted), widespread creation could clutter the system or create confusion in shared dashboards.
From the tool's definition Tool name is 'create_card' and description states 'Create a new question/card in Metabase'. The word 'Create' indicates data creation/modification.
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 MCP, 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 MCP, 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 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_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. 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 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