get_top_queries
AI agents call get_top_queries to retrieve information from Fluid Postgres without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name indicates it retrieves information about top queries, which is a read operation (querying metadata/statistics). Despite the empty description, the sibling tools on this server include clearly read-only operations (list_*, explain_*, analyze_*), suggesting this tool follows the same pattern. No indicators of destructive, write, execute, or financial operations are present.
From the tool's definition Tool name 'get_top_queries' combined with context that this is a PostgreSQL MCP server with other sibling read-oriented tools (list_objects, list_schemas, analyze_db_health, explain_query).
Attacks that exploit this kind of access
get_top_queries. It is categorised as a Read tool in the Fluid Postgres MCP Server, which means it retrieves data without modifying state.
Register the Fluid 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 Fluid 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 Fluid Postgres MCP server (povesma/fluid-postgres-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_top_queries is one line of Fluid Postgres's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →