List configured Postgres connections and their access mode, row cap, and timeout. ALWAYS call this first before issuing queries so you know which connections are read-only and won
AI agents call list_connections to retrieve information from Postgres Mcp Query Tool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about configured database connections (access mode, row cap, timeout) without executing queries, modifying data, or triggering external operations. It is a safe read-only introspection tool. The low severity reflects that exposing connection configuration metadata poses minimal risk compared to actual query execution or data modification.
From the tool's definition Tool name is 'list_connections' and description states it 'List configured Postgres connections and their access mode, row cap, and timeout.' This is purely informational retrieval with no data modification, execution, or side effects.
Attacks that exploit this kind of access
List configured Postgres connections and their access mode, row cap, and timeout. ALWAYS call this first before issuing queries so you know which connections are read-only and won. It is categorised as a Read tool in the Postgres Mcp Query Tool MCP Server, which means it retrieves data without modifying state.
Register the Postgres Mcp Query Tool MCP server in PolicyLayer and add a rule for list_connections: 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 Query Tool. Nothing to install.
list_connections 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 list_connections 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 list_connections. 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.
list_connections is provided by the Postgres Mcp Query Tool MCP server (nskha101/postgres-mcp-query-tool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →