// MCP TOOL REFERENCE

execute_card

Execute a Metabase question/card and get results

Part of the Metabase Analytics Integration Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

ryanmaule/metabase-mcp Execute Risk 3/5

// WHEN AI AGENTS USE THIS TOOL

AI agents invoke execute_card to trigger processes or run actions in Metabase Analytics Integration Server. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

// WHY ENFORCE A POLICY ON EXECUTE_CARD

execute_card can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

// RECOMMENDED POLICY

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

ryanmaule-metabase-mcp.yaml

tools:
  execute_card:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Metabase Analytics Integration Server policy for all 16 tools.

// DETAILS

Tool Name execute_card

Category Execute

MCP Server Metabase Analytics Integration Server MCP Server

Risk Level High

// MORE METABASE ANALYTICS INTEGRATION SERVER TOOLS

Destructive delete_dashboard Execute execute_query Write add_card_to_dashboard Write create_card Write create_collection Write create_dashboard Write update_card_visualization Write update_dashboard

View all 16 tools →

// WHAT CAN GO WRONG

Agents calling execute-class tools like execute_card have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER EXECUTE TOOLS ACROSS MCP SERVERS

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

Agent Passport System — Cryptographic Identity for AI Agents commerce_preflight Agent Passport System — Cryptographic Identity for AI Agents execute_with_context Agent Passport System — Cryptographic Identity for AI Agents gateway_execute_approval Agent Passport System — Cryptographic Identity for AI Agents governance_360 Agent Passport System — Cryptographic Identity for AI Agents parse_governance_block_html AgentClear — API Marketplace for AI Agents call_service

// IN CONTEXT OF HIGH RISK

execute_card is one of the high-risk operations in Metabase Analytics Integration Server. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

// RELATED READING

// FAQ

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.

How do I enforce a policy on execute_card? +

Add a rule in your Intercept YAML policy under the tools section for execute_card. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Metabase Analytics Integration Server MCP server.

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 Intercept 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 Intercept 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 (ryanmaule/metabase-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

execute_card

Enforce policies on Metabase Analytics Integration Server