Analyze active query execution plans and their performance characteristics.
AI agents call analyze_query_plans to retrieve information from Postgres without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes query execution plans—performance diagnostic information—without modifying data, executing queries, or triggering external operations. It is purely informational/observational in nature, consistent with Read category tools like 'get' or 'fetch'.
From the tool's definition Tool name 'analyze_query_plans' and description 'Analyze active query execution plans and their performance characteristics' indicate inspection and diagnostics of existing query performance data without modification, deletion, or command execution.
Documented attack patterns abuse exactly the kind of access analyze_query_plans gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Postgres, and nothing reaches the server without passing your rules. This is the rule we recommend for analyze_query_plans:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_query_plans": {}
}
}analyze_query_plans is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Analyze active query execution plans and their performance characteristics. It is categorised as a Read tool in the Postgres MCP Server, which means it retrieves data without modifying state.
Register the Postgres MCP server in PolicyLayer and add a rule for analyze_query_plans: 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 Postgres. Nothing to install.
analyze_query_plans 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 analyze_query_plans 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 analyze_query_plans. 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.
analyze_query_plans is provided by the Postgres MCP server (mukul975/postgres-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Postgres, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
239 Postgres tools catalogued and risk-classified — across an index of 43,000+ MCP servers.