explain_query

A read tool on the Mcpg MCP server.

SERVERMcpg SOURCEpypi:mcpg

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-devopam-mcpg/explain-query.md

WHAT IT DOES

What explain_query does on Mcpg

AI agents call explain_query to retrieve information from Mcpg without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why explain_query is rated Low

EXPLAIN/query explanation is a read-only operation that retrieves and displays query execution plans without modifying, executing, or deleting data. The empty description reduces confidence slightly, but the function name and context of sibling tools strongly suggest diagnostic/analysis purpose typical of PostgreSQL EXPLAIN commands.

From the tool's definition Tool name 'explain_query' indicates query plan analysis/explanation functionality. The sibling tools on this PostgreSQL MCP server include other analysis tools like 'analyze_query_plan', 'analyze_lock_hotspots', and similar read-only diagnostic operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs explain_query safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcpg, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For explain_query, this is the rule to start with:

explain_query Allowed

explain_query is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "explain_query": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcpg, apply this rule, and every explain_query call is checked against it from then on.

FAQ

Questions about explain_query

What does the explain_query tool do? +

explain_query is a read tool on the Mcpg MCP server. It is categorised as a Read tool in the Mcpg MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on explain_query? +

Register the Mcpg 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 Mcpg. Nothing to install.

What risk level is explain_query? +

explain_query is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit explain_query? +

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.

How do I block explain_query completely? +

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.

What MCP server provides explain_query? +

explain_query is provided by the Mcpg MCP server (pypi:mcpg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcpg, and thousands of servers like it.

This server

All 252 Mcpg tools →

Across the catalogue

claude_query on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →