vacuum_analyze · PostgreSQL MCP Server MCP: Risk & Policy

WHAT IT DOES

What vacuum_analyze does on PostgreSQL MCP Server

AI agents invoke vacuum_analyze to trigger actions in PostgreSQL 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 vacuum_analyze needs a policy

VACUUM ANALYZE triggers a database maintenance operation that modifies internal storage structures and statistics, but does not delete user data or irreversibly destroy records. It is an operational command that executes an internal PostgreSQL process. While it has side effects (reclaiming dead tuples, updating pg_statistic), these are non-destructive maintenance actions.

From the tool's definition "Run VACUUM ANALYZE on a table or database" — VACUUM ANALYZE is a PostgreSQL maintenance operation that reclaims storage and updates query planner statistics

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vacuum_analyze Rate-limited

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": {
    "vacuum_analyze": {
      "limits": [
        {
          "counter": "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 PostgreSQL MCP Server, so you can run agents against it safely.

FAQ

Questions about vacuum_analyze

What does the vacuum_analyze tool do? +

Run VACUUM ANALYZE on a table or database. It is categorised as a Execute tool in the PostgreSQL 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 vacuum_analyze? +

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

What risk level is vacuum_analyze? +

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

Can I rate-limit vacuum_analyze? +

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

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

vacuum_analyze is provided by the PostgreSQL MCP Server MCP server (reckersai/mcpg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.