List currently running queries from pg_stat_activity. Optionally filter by minimum duration in seconds. Shows PID, user, database, state, query text, duration, and wait events. Useful for identifying slow or stuck queries.
AI agents call getActiveQueries to retrieve information from Postgresql without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure read operation that queries system catalogs to display monitoring information. It has no side effects and does not modify, execute, or delete any data. The blast radius of misuse is minimal—an agent could only gain visibility into currently executing queries, which is informational only. It does not permit query execution, cancellation, or data modification.
From the tool's definition Tool 'getActiveQueries' retrieves and lists currently running queries from pg_stat_activity system table. Description explicitly states it 'List currently running queries' and 'Shows PID, user, database, state, query text, duration, and wait events.' No…
Attacks that exploit this kind of access
List currently running queries from pg_stat_activity. Optionally filter by minimum duration in seconds. Shows PID, user, database, state, query text, duration, and wait events. Useful for identifying slow or stuck queries. It is categorised as a Read tool in the Postgresql MCP Server, which means it retrieves data without modifying state.
Register the Postgresql MCP server in PolicyLayer and add a rule for getActiveQueries: 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 Postgresql. Nothing to install.
getActiveQueries 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 getActiveQueries 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 getActiveQueries. 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.
getActiveQueries is provided by the Postgresql MCP server (vnikhilbuddhavarapu/postgresql-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
getActiveQueries is one line of Postgresql'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 →