run_query · Sql Explorer MCP: Risk & Policy

WHAT IT DOES

What run_query does on Sql Explorer

AI agents invoke run_query to trigger actions in Sql Explorer. 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 run_query needs a policy

Despite the server being described as 'read-only', the tool name 'run_query' strongly implies execution of SQL queries. The server's emphasis on 'three-layer safety using AST validation and linting' suggests the tool actually runs queries against databases and safety measures are needed to prevent destructive operations.

From the tool's definition Tool name 'run_query' combined with server description mentioning 'AST validation and linting' as safety layers, implying query execution occurs. Description is empty, reducing confidence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_query Rate-limited

run_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": {
    "run_query": {
      "limits": [
        {
          "counter": "run_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 Sql Explorer, so you can run agents against it safely.

FAQ

Questions about run_query

What does the run_query tool do? +

run_query. It is categorised as a Execute tool in the Sql Explorer MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_query? +

Register the Sql Explorer MCP server in PolicyLayer and add a rule for run_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 Sql Explorer. Nothing to install.

What risk level is run_query? +

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

Can I rate-limit run_query? +

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

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

run_query is provided by the Sql Explorer MCP server (pawansingh3889/sql-explorer-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

run_query is one line of Sql Explorer's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →