PostgreSQL_check_long_running_queries
Check for queries that have been running longer than the specified duration.
This record as markdown: /tools/mukul975-postgres-mcp-server/postgresql-check-long-running-queries.md
What PostgreSQL_check_long_running_queries does on Postgres
AI agents call PostgreSQL_check_long_running_queries to retrieve information from Postgres without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why PostgreSQL_check_long_running_queries is rated Low
This tool retrieves and reports information about long-running queries from PostgreSQL system tables (likely pg_stat_statements or similar). It performs a read-only query against database metadata to identify performance issues. There is no capability to modify data, execute arbitrary code, delete information, or create financial obligations.
From the tool's definition Tool description states 'Check for queries that have been running longer than the specified duration' — a monitoring/inspection operation with no modification or execution of queries, only querying system state for diagnostics.
Attacks that exploit this kind of access
The rule that runs PostgreSQL_check_long_running_queries safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Postgres, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For PostgreSQL_check_long_running_queries, this is the rule to start with:
PostgreSQL_check_long_running_queries is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Postgres, apply this rule, and every PostgreSQL_check_long_running_queries call is checked against it from then on.
Questions about PostgreSQL_check_long_running_queries
Check for queries that have been running longer than the specified duration. 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 PostgreSQL_check_long_running_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.
PostgreSQL_check_long_running_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 PostgreSQL_check_long_running_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 PostgreSQL_check_long_running_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.
PostgreSQL_check_long_running_queries is provided by the Postgres MCP server (mukul975/postgres-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Postgres, and thousands of servers like it.
This server
Across the catalogue