pg_count

Count rows in a table, optionally with a WHERE clause or specific column.

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-count.md

WHAT IT DOES

What pg_count does on PostgreSQL MCP Server

AI agents call pg_count 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_count is rated Low

This tool performs a SELECT COUNT(*) operation with optional filtering. It retrieves information from the database but has no side effects—it does not create, modify, delete, or execute arbitrary operations. The WHERE clause and column specification are read-only query parameters. This is a straightforward data retrieval operation with minimal blast radius even if misused by an agent.

From the tool's definition Tool name 'pg_count' and description 'Count rows in a table, optionally with a WHERE clause or specific column' indicates a query operation that retrieves aggregate data without modifying or deleting any data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

pg_count Allowed

pg_count 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_count": {}
  }
}

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

FAQ

Questions about pg_count

What does the pg_count tool do? +

Count rows in a table, optionally with a WHERE clause or specific column. 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_count? +

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

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

Can I rate-limit pg_count? +

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

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

pg_count 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_count does on PostgreSQL MCP Server

Why pg_count is rated Low

The rule that runs pg_count safely

Questions about pg_count

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