pg_detect_query_anomalies

Detects queries deviating from their historical execution time norms

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-detect-query-anomalies.md

What pg_detect_query_anomalies does on PostgreSQL MCP Server

AI agents call pg_detect_query_anomalies 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_detect_query_anomalies is rated Low

This tool analyzes historical query execution metrics to identify anomalies—a pure read operation that queries existing performance data. It has no side effects, does not execute queries, does not modify data, and does not delete anything. The blast radius of misuse is minimal; an agent could only retrieve diagnostic information about query performance patterns.

From the tool's definition Tool name 'pg_detect_query_anomalies' and description 'Detects queries deviating from their historical execution time norms' indicate a monitoring/analytical operation that retrieves and analyzes query performance data without modifying, executing, or…

Questions about pg_detect_query_anomalies

What does the pg_detect_query_anomalies tool do? +

Detects queries deviating from their historical execution time norms. 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_detect_query_anomalies? +

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

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

Can I rate-limit pg_detect_query_anomalies? +

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

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

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

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