test_query · Metabase Mcp Navi MCP: Risk & Policy

WHAT IT DOES

What test_query does on Metabase Mcp Navi

AI agents invoke test_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 test_query needs a policy

Given the server's explicit purpose includes query execution and sibling tools include 'execute_card', a 'test_query' tool most likely runs or tests a database query. Executing arbitrary queries can have significant side effects depending on the query content. Confidence is reduced due to the empty description, but the name and server context suggest Execute category.

From the tool's definition Tool name 'test_query' on a server that provides 'query execution' capabilities; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

test_query Rate-limited

test_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": {
    "test_query": {
      "limits": [
        {
          "counter": "test_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 test_query

What does the test_query tool do? +

test_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 test_query? +

Register the Metabase Mcp Navi MCP server in PolicyLayer and add a rule for test_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 test_query? +

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

Can I rate-limit test_query? +

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

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

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