New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

PostgreSQL_vacuum_progress_monitoring

Monitor active vacuum operations and their performance impact.

SERVERPostgres SOURCEmukul975/postgres-mcp-server
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/mukul975-postgres-mcp-server/postgresql-vacuum-progress-monitoring.md

What PostgreSQL_vacuum_progress_monitoring does on Postgres

AI agents call PostgreSQL_vacuum_progress_monitoring to retrieve information from Postgres without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why PostgreSQL_vacuum_progress_monitoring is rated Low

This is a diagnostic and observational tool that retrieves the state of active VACUUM operations in PostgreSQL. VACUUM is a maintenance operation that runs independently; this tool only observes and reports on its progress and performance metrics. It has no side effects, performs no modifications to the database, and cannot alter or delete data.

From the tool's definition The tool 'PostgreSQL_vacuum_progress_monitoring' is described as 'Monitor active vacuum operations and their performance impact.' The key verb is 'Monitor' which indicates observation and retrieval of status information about ongoing vacuum operations.

Questions about PostgreSQL_vacuum_progress_monitoring

What does the PostgreSQL_vacuum_progress_monitoring tool do? +

Monitor active vacuum operations and their performance impact. It is categorised as a Read tool in the Postgres MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on PostgreSQL_vacuum_progress_monitoring? +

Register the Postgres MCP server in PolicyLayer and add a rule for PostgreSQL_vacuum_progress_monitoring: 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 Postgres. Nothing to install.

What risk level is PostgreSQL_vacuum_progress_monitoring? +

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

Can I rate-limit PostgreSQL_vacuum_progress_monitoring? +

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

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

PostgreSQL_vacuum_progress_monitoring is provided by the Postgres MCP server (mukul975/postgres-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Postgres, 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 Postgres'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.