Return the execution plan for a query (without running it for results).
AI agents call explain_query to retrieve information from Sql Explorer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
explain_query is purely informational—it retrieves metadata about query execution strategy without executing the query itself, modifying data, or causing side effects. This is a safe, read-only diagnostic operation. While it's part of a SQL-enabled server, the tool specifically avoids execution and data retrieval, placing it in the Read category with low severity.
From the tool's definition Tool returns only an execution plan (EXPLAIN output) without running the query or returning data results. The description explicitly states it analyzes the query 'without running it for results.' The server is documented as 'Read-only' with 'three-layer…
Attacks that exploit this kind of access
Return the execution plan for a query (without running it for results). It is categorised as a Read tool in the Sql Explorer MCP Server, which means it retrieves data without modifying state.
Register the Sql Explorer MCP server in PolicyLayer and add a rule for explain_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.
explain_query is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the explain_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.
Set action: deny in the PolicyLayer policy for explain_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.
explain_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →