executeQuery · SQL MCP Server MCP: Risk & Policy

WHAT IT DOES

What executeQuery does on SQL MCP Server

AI agents invoke executeQuery to trigger actions in SQL 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 executeQuery needs a policy

Despite the server's read-only claim and security features, this tool executes arbitrary SQL queries against a database. The actual read-only enforcement depends on implementation and configuration. Misuse could expose sensitive data at scale, and the tool fundamentally runs code/queries rather than just retrieving predefined data, placing it in Execute.

From the tool's definition Tool name 'executeQuery' and description '执行只读 SQL 查询' (Execute read-only SQL query). Server claims read-only and injection protection, but arbitrary SQL execution is still Execute category.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

executeQuery Rate-limited

executeQuery 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": {
    "executeQuery": {
      "limits": [
        {
          "counter": "executequery_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 MCP Server, so you can run agents against it safely.

FAQ

Questions about executeQuery

What does the executeQuery tool do? +

执行只读 SQL 查询. It is categorised as a Execute tool in the SQL 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 executeQuery? +

Register the SQL MCP Server MCP server in PolicyLayer and add a rule for executeQuery: 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 MCP Server. Nothing to install.

What risk level is executeQuery? +

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

Can I rate-limit executeQuery? +

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

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

executeQuery is provided by the SQL MCP Server MCP server (polarisxb/sql-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.