AI agents call get_top_queries to retrieve information from Postgres Mcp Legacy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves query metrics or statistics without modifying data. However, the empty description reduces confidence slightly. The 'top queries' pattern typically refers to performance monitoring (e.g., queries by execution time or frequency), which could expose sensitive information about application behavior and schema structure if accessed by an unauthorized agent.
From the tool's definition Tool name 'get_top_queries' indicates retrieval of query performance data from PostgreSQL. The sibling tools on this server (explain_query, analyze_db_health, backup_*) are database diagnostic and operational tools, contextually confirming a Read operation.
Documented attack patterns abuse exactly the kind of access get_top_queries gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Postgres Mcp Legacy, and nothing reaches the server without passing your rules. This is the rule we recommend for get_top_queries:
{
"version": "1",
"default": "deny",
"tools": {
"get_top_queries": {}
}
}get_top_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. It is categorised as a Read tool in the Postgres Mcp Legacy MCP Server, which means it retrieves data without modifying state.
Register the Postgres Mcp Legacy 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 Legacy. 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 Legacy MCP server (neverinfamous/postgres-mcp-legacy). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Postgres Mcp Legacy, 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.
60 Postgres Mcp Legacy tools catalogued and risk-classified — across an index of 43,000+ MCP servers.