execute_card_query · Metabase MCP Server MCP: Risk & Policy

WHAT IT DOES

What execute_card_query does on Metabase MCP Server

AI agents invoke execute_card_query 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_query needs a policy

This tool executes queries against a database through Metabase. Although it is read-only (does not modify data), execution tools that trigger resource-intensive operations against external systems are classified as Execute rather than Read.

From the tool's definition Tool name contains 'execute' and description states 'Execute a saved card query and return results' and 'executes queries that may be slow or resource-intensive.' The tool runs queries against a Metabase instance, which are external operations whose effects…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_card_query Rate-limited

execute_card_query 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_query": {
      "limits": [
        {
          "counter": "execute_card_query_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_query

What does the execute_card_query tool do? +

▶️ [MODERATE RISK] Execute a saved card query and return results. Use this to get actual data from a card. May take time for complex queries. Risk: Moderate - executes queries that may be slow or resource-intensive. Does not modify data. 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_query? +

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

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

Can I rate-limit execute_card_query? +

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

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

execute_card_query is provided by the Metabase MCP Server MCP server (mikela92/metabase-mcp-mab). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.