pg_stats_distribution
Analyze data distribution with histogram buckets, skewness, and kurtosis. Use groupBy to get distribution per category.
This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-stats-distribution.md
What pg_stats_distribution does on PostgreSQL MCP Server
AI agents call pg_stats_distribution 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.
Why pg_stats_distribution is rated Low
This tool performs statistical analysis and querying of existing data to compute distribution metrics. It is a read-only analytical operation that retrieves and computes statistics without altering, deleting, or executing code. The groupBy parameter enables filtering and aggregation but remains a query/retrieval operation. Low severity because data analysis poses minimal risk even if misused by an AI agent.
From the tool's definition Tool analyzes data distribution with histogram buckets, skewness, and kurtosis using groupBy to retrieve distribution metrics. Keywords: 'Analyze', 'distribution' (data analysis), 'histogram' (statistical query output).
Attacks that exploit this kind of access
The rule that runs pg_stats_distribution 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_distribution, this is the rule to start with:
pg_stats_distribution is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect PostgreSQL MCP Server, apply this rule, and every pg_stats_distribution call is checked against it from then on.
Questions about pg_stats_distribution
Analyze data distribution with histogram buckets, skewness, and kurtosis. Use groupBy to get distribution per category. It is categorised as a Read tool in the PostgreSQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for pg_stats_distribution: 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.
pg_stats_distribution 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 pg_stats_distribution 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 pg_stats_distribution. 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.
pg_stats_distribution 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.
More on PostgreSQL MCP Server, and thousands of servers like it.
This server
Across the catalogue