analyzeTable · Postgresql MCP: Risk & Policy

WHAT IT DOES

What analyzeTable does on Postgresql

AI agents invoke analyzeTable to trigger actions in Postgresql. 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 analyzeTable needs a policy

ANALYZE is a database operation that modifies internal planner statistics, not just reading data. It is not destructive (it doesn't delete user data), not a write to user-visible data, but it does execute a server-side operation with real side effects. Misuse could degrade or alter query planning behavior across the database, hence medium severity.

From the tool's definition 'Run ANALYZE on a table to update query planner statistics' — triggers a PostgreSQL ANALYZE operation, an external database command with side effects (updating internal statistics).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

analyzeTable Rate-limited

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

FAQ

Questions about analyzeTable

What does the analyzeTable tool do? +

Run ANALYZE on a table to update query planner statistics. This helps PostgreSQL choose optimal query plans. Run after large data changes (bulk imports, mass updates/deletes). It is categorised as a Execute tool in the Postgresql MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on analyzeTable? +

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

What risk level is analyzeTable? +

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

Can I rate-limit analyzeTable? +

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

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

analyzeTable is provided by the Postgresql MCP server (vnikhilbuddhavarapu/postgresql-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.