execute_card · Metabase MCP Server MCP: Risk & Policy

WHAT IT DOES

What execute_card does on Metabase MCP Server

AI agents invoke execute_card to trigger actions in Metabase MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why execute_card needs a policy

While the tool executes an existing card (query) rather than arbitrary code, it triggers external query operations whose effects depend on the card's configuration and arguments. The results are data retrieval, but the execution itself—running queries against databases—constitutes an Execute action.

From the tool's definition Tool description states 'Run a Metabase card query and return the actual data results' and 'programmatically access query results for further processing'. The verb 'Run' indicates execution of a pre-defined query.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_card Rate-limited

execute_card stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_card": {
      "limits": [
        {
          "counter": "execute_card_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 execute_card

What does the execute_card tool do? +

Run a Metabase card query and return the actual data results - use this to get current data from existing cards, refresh analytical insights, or programmatically access query results for further processing. It is categorised as a Execute tool in the Metabase MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_card? +

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

execute_card is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_card? +

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

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

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