pg_stats_moving_avg

Calculate moving average (AVG OVER sliding window) for a numeric column. Specify windowSize for the number of preceding rows to include.

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-moving-avg.md

What pg_stats_moving_avg does on PostgreSQL MCP Server

AI agents call pg_stats_moving_avg 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_moving_avg is rated Low

This tool retrieves and computes aggregate statistics from a numeric column using window functions. It does not create, modify, delete, or execute arbitrary code—it only queries and calculates results. The blast radius of misuse is minimal: at worst, an agent could request expensive computations, but no data integrity or system state is affected. This is a straightforward Read operation.

From the tool's definition Tool description: 'Calculate moving average (AVG OVER sliding window) for a numeric column.' The AVG OVER clause is a SQL analytic function that computes aggregate statistics over a window of rows without modifying data.

Questions about pg_stats_moving_avg

What does the pg_stats_moving_avg tool do? +

Calculate moving average (AVG OVER sliding window) for a numeric column. Specify windowSize for the number of preceding rows to include. 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_moving_avg? +

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

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

Can I rate-limit pg_stats_moving_avg? +

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

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

pg_stats_moving_avg 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of PostgreSQL MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.