pg_stat_activity

Get currently running queries and connections.

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-stat-activity.md

WHAT IT DOES

What pg_stat_activity does on PostgreSQL MCP Server

AI agents call pg_stat_activity 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_stat_activity is rated Low

This tool retrieves system activity data from PostgreSQL's pg_stat_activity view. It queries existing state information without side effects, modifications, or execution of arbitrary code. The blast radius of misuse is minimal—an agent could observe running queries and connections but cannot alter data, execute commands, or cause destructive operations.

From the tool's definition Tool name 'pg_stat_activity' and description 'Get currently running queries and connections' indicate pure data retrieval with no modification or execution capabilities.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

pg_stat_activity Allowed

pg_stat_activity 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_stat_activity": {}
  }
}

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_stat_activity call is checked against it from then on.

FAQ

Questions about pg_stat_activity

What does the pg_stat_activity tool do? +

Get currently running queries and connections. 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_stat_activity? +

Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for pg_stat_activity: 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_stat_activity? +

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

Can I rate-limit pg_stat_activity? +

Yes. Add a rate_limit block to the pg_stat_activity 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_stat_activity completely? +

Set action: deny in the PolicyLayer policy for pg_stat_activity. 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_stat_activity? +

pg_stat_activity 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_stat_activity does on PostgreSQL MCP Server

Why pg_stat_activity is rated Low

The rule that runs pg_stat_activity safely

Questions about pg_stat_activity

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