get_top_queries
AI agents call get_top_queries to retrieve information from Postgres MCP Pro without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to query and return metadata about top-performing or top-consuming queries from the database, which is consistent with read-only monitoring operations. The server focuses on analysis (explain plans, health checks) rather than modification. With no description, confidence is moderate, but the name and context strongly suggest data retrieval without side effects.
From the tool's definition Tool name 'get_top_queries' suggests retrieval of query statistics; context of sibling tools (analyze_db_health, explain_query, list_objects, list_schemas) indicates this is a diagnostic/monitoring function. No description provided limits certainty.
Attacks that exploit this kind of access
get_top_queries. It is categorised as a Read tool in the Postgres MCP Pro MCP Server, which means it retrieves data without modifying state.
Register the Postgres MCP Pro 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 MCP Pro. 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 Pro MCP server (luislopezsanchez/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 →