Get top queries by total time, calls, and mean time from pg_stat_statements.
AI agents call PostgreSQL_get_top_heavy_queries 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 reads performance statistics from PostgreSQL's built-in pg_stat_statements extension. It retrieves aggregated query metrics (total time, call counts, mean time) for analysis and monitoring purposes. There are no side effects, no data modification, and no code execution triggered by the tool itself. The worst-case misuse is information disclosure of query patterns, which is a low severity read risk.
From the tool's definition Tool queries pg_stat_statements to retrieve statistics on top queries; description indicates data retrieval ('Get top queries') with no modification, deletion, or execution of arbitrary code.
Documented attack patterns abuse exactly the kind of access PostgreSQL_get_top_heavy_queries 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_get_top_heavy_queries:
{
"version": "1",
"default": "deny",
"tools": {
"PostgreSQL_get_top_heavy_queries": {}
}
}PostgreSQL_get_top_heavy_queries 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.
Get top queries by total time, calls, and mean time from pg_stat_statements. 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_get_top_heavy_queries: 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_get_top_heavy_queries 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_get_top_heavy_queries 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_get_top_heavy_queries. 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_get_top_heavy_queries 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.