pg_stats_frequency
Get value frequency distribution (count per unique value) ordered by frequency descending. Shows the most common values first.
This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-stats-frequency.md
What pg_stats_frequency does on PostgreSQL MCP Server
AI agents call pg_stats_frequency 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_frequency is rated Low
This is a statistics query tool that analyzes and retrieves distribution data from an existing table or column. It has no side effects, does not modify data, and poses minimal risk if misused by an AI agent—the worst outcome would be returning statistical information that may already be available through other channels.
From the tool's definition Tool retrieves a frequency distribution ('count per unique value') from PostgreSQL statistics, ordered by frequency. The action is 'Get' and 'Shows', indicating data retrieval only.
Attacks that exploit this kind of access
The rule that runs pg_stats_frequency 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_frequency, this is the rule to start with:
pg_stats_frequency 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_frequency call is checked against it from then on.
Questions about pg_stats_frequency
Get value frequency distribution (count per unique value) ordered by frequency descending. Shows the most common values first. 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_frequency: 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_frequency 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_frequency 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_frequency. 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_frequency 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