pg_stats_distinct

Get distinct values from a column with count. Useful for understanding cardinality and unique value distribution.

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-stats-distinct.md

WHAT IT DOES

What pg_stats_distinct does on PostgreSQL MCP Server

AI agents call pg_stats_distinct 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_stats_distinct is rated Low

This tool performs a read-only statistical query to analyze column cardinality and value distribution. It queries existing data, produces no side effects, and cannot modify, delete, or execute arbitrary operations. The operation is informational and analytical in nature, making it a Read category risk with low severity.

From the tool's definition Tool name 'pg_stats_distinct' and description 'Get distinct values from a column with count' indicate a SELECT-based query operation that retrieves and aggregates existing data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

pg_stats_distinct Allowed

pg_stats_distinct 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_stats_distinct": {}
  }
}

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

FAQ

Questions about pg_stats_distinct

What does the pg_stats_distinct tool do? +

Get distinct values from a column with count. Useful for understanding cardinality and unique value distribution. 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_stats_distinct? +

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

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

Can I rate-limit pg_stats_distinct? +

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

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

pg_stats_distinct 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_stats_distinct does on PostgreSQL MCP Server

Why pg_stats_distinct is rated Low

The rule that runs pg_stats_distinct safely

Questions about pg_stats_distinct

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