Analyze query complexity by examining execution plans and costs.
AI agents call PostgreSQL_analyze_query_complexity 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 examines query execution plan data and associated costs. It performs read-only inspection of PostgreSQL system catalogs and query statistics without executing queries against user data, modifying any schema, or triggering external operations. The blast radius of misuse is minimal—worst case an agent wastes resources analyzing harmless queries.
From the tool's definition Tool analyzes execution plans and costs with no modification capability. The word 'analyze' combined with 'examining' indicates passive inspection of existing query metadata. No CREATE, UPDATE, DELETE, DROP, or execution keywords present.
Documented attack patterns abuse exactly the kind of access PostgreSQL_analyze_query_complexity 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 PostgreSQL_analyze_query_complexity:
{
"version": "1",
"default": "deny",
"tools": {
"PostgreSQL_analyze_query_complexity": {}
}
}PostgreSQL_analyze_query_complexity 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 query complexity by examining execution plans and costs. 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 PostgreSQL_analyze_query_complexity: 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.
PostgreSQL_analyze_query_complexity 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 PostgreSQL_analyze_query_complexity 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 PostgreSQL_analyze_query_complexity. 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.
PostgreSQL_analyze_query_complexity 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.