execute_query_builder_card · Metabase MCP Server MCP

WHAT IT DOES

What execute_query_builder_card does on Metabase MCP Server

AI agents invoke execute_query_builder_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_query_builder_card needs a policy

This tool executes arbitrary query-builder cards with custom parameters, which constitutes triggering external database operations whose effects depend on the parameters provided. Although the description labels it 'MODERATE RISK,' the actual capability to execute queries with custom filters and aggregations that could consume significant resources warrants 'high' severity.

From the tool's definition Tool name contains 'execute' and description explicitly states 'Execute a query-builder card' and 'executes queries that may be slow or resource-intensive.' The description also flags '[MODERATE RISK]' and warns of potential resource-intensive operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_query_builder_card Rate-limited

execute_query_builder_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_query_builder_card": {
      "limits": [
        {
          "counter": "execute_query_builder_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_query_builder_card

What does the execute_query_builder_card tool do? +

⚙️ [MODERATE RISK] Execute a query-builder card with specific parameters. Use this to run query builder cards with custom filters and aggregations. Risk: Moderate - executes queries that may be slow or resource-intensive. 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_query_builder_card? +

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

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

Can I rate-limit execute_query_builder_card? +

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

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

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