postgres_vacuum_analyze · Multi-Database MCP Server MCP

WHAT IT DOES

What postgres_vacuum_analyze does on Multi-Database MCP Server

AI agents invoke postgres_vacuum_analyze to trigger actions in Multi-Database MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why postgres_vacuum_analyze needs a policy

VACUUM ANALYZE is a PostgreSQL maintenance operation that reclaims storage and updates query planner statistics. It does not delete user data destructively (VACUUM reclaims dead tuples already marked for deletion), but it does execute a significant database operation that can lock tables (especially FULL mode), consume I/O resources, and affect database performance.

From the tool's definition 'Run VACUUM ANALYZE on a table for maintenance (requires FULL mode)'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

postgres_vacuum_analyze Rate-limited

postgres_vacuum_analyze stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "postgres_vacuum_analyze": {
      "limits": [
        {
          "counter": "postgres_vacuum_analyze_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Multi-Database MCP Server, so you can run agents against it safely.

FAQ

Questions about postgres_vacuum_analyze

What does the postgres_vacuum_analyze tool do? +

Run VACUUM ANALYZE on a table for maintenance (requires FULL mode). It is categorised as a Execute tool in the Multi-Database MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on postgres_vacuum_analyze? +

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

What risk level is postgres_vacuum_analyze? +

postgres_vacuum_analyze is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit postgres_vacuum_analyze? +

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

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

postgres_vacuum_analyze is provided by the Multi-Database MCP Server MCP server (nam088/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.