analyze_query_plans
Analyze active query execution plans and their performance characteristics.
This record as markdown: /tools/mukul975-postgres-mcp-server/analyze-query-plans.md
What analyze_query_plans does on Postgres
AI agents call analyze_query_plans to retrieve information from Postgres without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why analyze_query_plans is rated Low
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.
Attacks that exploit this kind of access
The rule that runs analyze_query_plans safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Postgres, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For analyze_query_plans, this is the rule to start with:
analyze_query_plans is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Postgres, apply this rule, and every analyze_query_plans call is checked against it from then on.
Questions about analyze_query_plans
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.
More on Postgres, and thousands of servers like it.
This server
Across the catalogue