PostgreSQL_longest_idle_transactions

What PostgreSQL_longest_idle_transactions does on Postgres

AI agents call PostgreSQL_longest_idle_transactions 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_longest_idle_transactions is rated Low

This tool performs diagnostic inspection of PostgreSQL transaction metadata to identify long-running idle transactions. It does not modify data, execute arbitrary queries, or trigger external actions. It falls squarely into the Read category as a monitoring/diagnostic tool. Severity is low because misuse would only expose transaction state information, not compromise data or cause destructive changes.

From the tool's definition Tool name and description indicate it 'find[s] transactions' in an idle state—a query/monitoring operation. The verb 'find' is a read operation that retrieves information about transaction state without modifying or executing against the database.

The rule that runs PostgreSQL_longest_idle_transactions 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_longest_idle_transactions, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "PostgreSQL_longest_idle_transactions": {}
  }
}

Questions about PostgreSQL_longest_idle_transactions