AI agents call get_top_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.
get_top_queries retrieves and analyzes pre-recorded query performance metadata from pg_stat_statements. It has no side effects: it does not execute queries, modify database state, or delete data. The blast radius of misuse is minimal—an AI might surface internal query patterns but cannot cause operational harm. This is a pure Read operation.
From the tool's definition Tool queries pg_stat_statements to 'Find slowest queries' and 'identify performance bottlenecks' — this is read-only diagnostic introspection of existing query statistics. The description contains no indication of modification, execution, or deletion.
Attacks that exploit this kind of access
Find slowest queries from pg_stat_statements. Requires pg_stat_statements extension enabled. Use this to identify performance bottlenecks. 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 get_top_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.
get_top_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 get_top_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 get_top_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.
get_top_queries is provided by the Postgres MCP server (teja-sudo/postgres-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →