copy_card · Metabase MCP Server MCP: Risk & Policy

WHAT IT DOES

What copy_card does on Metabase MCP Server

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

This tool creates new data (a duplicate card) reversibly within Metabase. It does not execute queries, delete data, or cause irreversible changes. While it creates new resources, this is a standard Write operation with moderate severity given it could accumulate unused cards or be misused to flood the system with duplicates, but the action is reversible (cards can be deleted).

From the tool's definition copy_card creates a duplicate copy of an existing Metabase card with identical query and settings - explicitly stated as creating new objects (duplicate, create)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

copy_card Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "copy_card": {
      "limits": [
        {
          "counter": "copy_card_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 copy_card

What does the copy_card tool do? +

Create a duplicate copy of an existing Metabase card with identical query and settings - use this to create variations of existing cards, build templates for similar analyses, or backup important queries before modifications. 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 copy_card? +

Register the Metabase MCP Server MCP server in PolicyLayer and add a rule for copy_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 Server. Nothing to install.

What risk level is copy_card? +

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

Can I rate-limit copy_card? +

Yes. Add a rate_limit block to the copy_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.

How do I block copy_card completely? +

Set action: deny in the PolicyLayer policy for copy_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.

What MCP server provides copy_card? +

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