List active connections from pg_stat_activity.
AI agents call list_active_connections to retrieve information from PostgreSQL SSH MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries pg_stat_activity, a read-only system catalog view in PostgreSQL that provides information about currently active connections and their status. It retrieves data with no side effects—no data is created, modified, deleted, or code is executed.
From the tool's definition Tool name 'list_active_connections' and description 'List active connections from pg_stat_activity' indicate a query operation that retrieves connection metadata from PostgreSQL's system view without modification.
Documented attack patterns abuse exactly the kind of access list_active_connections gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PostgreSQL SSH MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_active_connections:
{
"version": "1",
"default": "deny",
"tools": {
"list_active_connections": {}
}
}list_active_connections is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List active connections from pg_stat_activity. It is categorised as a Read tool in the PostgreSQL SSH MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PostgreSQL SSH MCP Server MCP server in PolicyLayer and add a rule for list_active_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 PostgreSQL SSH MCP Server. Nothing to install.
list_active_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_active_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_active_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_active_connections is provided by the PostgreSQL SSH MCP Server MCP server (zlash65/postgresql-ssh-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PostgreSQL SSH MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 PostgreSQL SSH MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.