execute_card

Execute a Metabase question/card and get results

SERVERMetabase Analytics Integration Server SOURCEzsh52013148087/metabase-mcp

High RISK CLASS

Category Execute

Parameters 20 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/zsh52013148087-metabase-mcp/execute-card.md

WHAT IT DOES

What execute_card does on Metabase Analytics Integration Server

AI agents invoke execute_card to trigger actions in Metabase Analytics Integration 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.

Parameter	Type	Required	Description
`card_id`	number	—	ID of the card/question to execute
`parameters`	object	—	Optional parameters for the query

Parameters from the server's own tool schema.

RISK

Why execute_card is rated High

This tool runs a pre-saved Metabase question/card, which is an operation that executes arbitrary queries against databases. While it does not create, modify, or destroy data (which would elevate it to Write or Destructive), execution of analytics queries can have side effects depending on the card's configuration—including accessing sensitive data, consuming resources, or triggering downstream actions.

From the tool's definition Tool name 'execute_card' combined with description 'Execute a Metabase question/card and get results' explicitly uses the verb 'Execute' and triggers external operations (query execution) whose effects depend on the card's definition and underlying data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs execute_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 execute_card, this is the rule to start with:

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.

The button opens the PolicyLayer dashboard: create your workspace, connect Metabase Analytics Integration Server, apply this rule, and every execute_card call is checked against it from then on.

FAQ

Questions about execute_card

What does the execute_card tool do? +

Execute a Metabase question/card and get results. It is categorised as a Execute tool in the Metabase Analytics Integration Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does execute_card accept? +

execute_card accepts 2 parameters: card_id, parameters. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on execute_card? +

Register the Metabase Analytics Integration 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 Analytics Integration 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 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.

KEEP EXPLORING

More on Metabase Analytics Integration Server, and thousands of servers like it.

This server

All 16 Metabase Analytics Integration Server tools → High-risk tools on this server →

Across the catalogue

claude_execute on Claude Bridge →execute_test_case on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →