pg_connection_stats

Get connection statistics by database and state.

SERVERPostgreSQL MCP Server SOURCE@neverinfamous/postgres-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-connection-stats.md

WHAT IT DOES

What pg_connection_stats does on PostgreSQL MCP Server

AI agents call pg_connection_stats to retrieve information from PostgreSQL MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why pg_connection_stats is rated Low

This tool retrieves connection statistics by filtering on database and state dimensions. It performs a read-only query operation with no side effects on database objects, configuration, or data. Low severity because connection statistics are generally non-sensitive operational metadata, and misuse would only allow an AI to observe existing connections, not create, modify, delete, or execute operations.

From the tool's definition Tool name and description both indicate a retrieval operation: 'Get connection statistics' with no mutation language. Queries database metadata/state without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pg_connection_stats safely

PolicyLayer is an MCP gateway: it sits between your AI agents and PostgreSQL MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pg_connection_stats, this is the rule to start with:

pg_connection_stats Allowed

pg_connection_stats is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect PostgreSQL MCP Server, apply this rule, and every pg_connection_stats call is checked against it from then on.

FAQ

Questions about pg_connection_stats

What does the pg_connection_stats tool do? +

Get connection statistics by database and state. It is categorised as a Read tool in the PostgreSQL MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pg_connection_stats? +

Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for pg_connection_stats: 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 MCP Server. Nothing to install.

What risk level is pg_connection_stats? +

pg_connection_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit pg_connection_stats? +

Yes. Add a rate_limit block to the pg_connection_stats 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.

How do I block pg_connection_stats completely? +

Set action: deny in the PolicyLayer policy for pg_connection_stats. 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.

What MCP server provides pg_connection_stats? +

pg_connection_stats is provided by the PostgreSQL MCP Server MCP server (@neverinfamous/postgres-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

What pg_connection_stats does on PostgreSQL MCP Server

Why pg_connection_stats is rated Low

The rule that runs pg_connection_stats safely

Questions about pg_connection_stats

More on PostgreSQL MCP Server, and thousands of servers like it.