move_cards · Metabase MCP Server MCP: Risk & Policy

WHAT IT DOES

What move_cards does on Metabase MCP Server

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

This tool modifies the state of Metabase cards by changing their collection or dashboard assignment, which is a Write operation (reversible data modification). While the move could disrupt dashboard layouts or user workflows if misapplied, it does not delete data, execute arbitrary code, or create financial risk.

From the tool's definition Tool performs 'Relocate multiple Metabase cards to a different collection or dashboard' - a reversible modification operation that changes the location/organization of existing analytics objects without deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_cards Rate-limited

move_cards 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": {
    "move_cards": {
      "limits": [
        {
          "counter": "move_cards_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 move_cards

What does the move_cards tool do? +

Relocate multiple Metabase cards to a different collection or dashboard for better organization - use this to reorganize analytical content, group related cards, or clean up workspace structure. 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 move_cards? +

Register the Metabase MCP Server MCP server in PolicyLayer and add a rule for move_cards: 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 move_cards? +

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

Can I rate-limit move_cards? +

Yes. Add a rate_limit block to the move_cards 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 move_cards completely? +

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

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