Get the EXPLAIN ANALYZE execution plan for a SQL query. The query runs inside a transaction that is always rolled back, so it never modifies data.
AI agents call explain_query to retrieve information from Mcp Postgres Query without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool explicitly states it always rolls back the transaction, preventing any data modification. EXPLAIN ANALYZE does execute the query internally but the rollback guarantee means no persistent side effects. It reads and returns the execution plan.
From the tool's definition 'Get the EXPLAIN ANALYZE execution plan for a SQL query. The query runs inside a transaction that is always rolled back, so it never modifies data.'
Attacks that exploit this kind of access
Get the EXPLAIN ANALYZE execution plan for a SQL query. The query runs inside a transaction that is always rolled back, so it never modifies data. It is categorised as a Read tool in the Mcp Postgres Query MCP Server, which means it retrieves data without modifying state.
Register the Mcp Postgres Query 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 Mcp Postgres Query. 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 Mcp Postgres Query MCP server (lordbasilaiassistant-sudo/mcp-postgres-query). 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 →