execute_query · Metabase Mcp Navi MCP: Risk & Policy

WHAT IT DOES

What execute_query does on Metabase Mcp Navi

AI agents invoke execute_query to trigger actions in Metabase Mcp Navi. 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 needs a policy

Query execution is a classic Execute category action because it triggers external operations (database queries) whose effects depend on arguments. While query execution alone does not inherently delete or modify data (those would be Destructive), a poorly constrained execute_query could allow an AI agent to run arbitrary SQL including UPDATE, INSERT, or DROP statements depending on database permissions.

From the tool's definition Tool name is 'execute_query' in a Metabase MCP server that provides 'direct access to dashboards, cards, and query execution.' The description is empty, but the name and server context clearly indicate this tool runs queries against a database.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_query Rate-limited

execute_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_query": {
      "limits": [
        {
          "counter": "execute_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 Navi, so you can run agents against it safely.

FAQ

Questions about execute_query

What does the execute_query tool do? +

execute_query. It is categorised as a Execute tool in the Metabase Mcp Navi 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? +

Register the Metabase Mcp Navi MCP server in PolicyLayer and add a rule for execute_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 Navi. Nothing to install.

What risk level is execute_query? +

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

Can I rate-limit execute_query? +

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

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

execute_query is provided by the Metabase Mcp Navi MCP server (manish-coder-1007/metabase-mcp-navi). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.