execute_native_query · Metabase MCP Server MCP

WHAT IT DOES

What execute_native_query does on Metabase MCP Server

AI agents invoke execute_native_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_native_query needs a policy

This tool allows execution of arbitrary SQL queries against a database. While it does not inherently delete or modify data (hence not Destructive), it can trigger any operation a SQL query supports—including SELECT, INSERT, UPDATE, or DROP statements depending on the arguments. The category Execute is most appropriate because the effects are operation-dependent and the tool directly executes code.

From the tool's definition Tool description explicitly states 'Execute an ad-hoc native SQL query directly against a database' and 'run custom SQL'. The warning label '[MODERATE RISK]' and truncated description emphasize its dangerous nature.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_native_query Rate-limited

execute_native_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_native_query": {
      "limits": [
        {
          "counter": "execute_native_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_native_query

What does the execute_native_query tool do? +

⚠️ [MODERATE RISK] Execute an ad-hoc native SQL query directly against a database. Use this when you need to run custom SQL that doesn\. 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_native_query? +

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

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

Can I rate-limit execute_native_query? +

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

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

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