analyze_table · Redshift MCP Server MCP: Risk & Policy

WHAT IT DOES

What analyze_table does on Redshift MCP Server

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

ANALYZE runs an active operation against the database to update internal statistics (e.g., row counts, column distributions). While it does not delete or modify user data, it is not a passive read — it causes the database engine to scan the table and write updated metadata/statistics. This places it in the Execute category.

From the tool's definition 'Analyze table to collect statistics information' — ANALYZE is a database command that executes a statistics-collection operation on a table, triggering real database activity beyond a simple read.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

analyze_table Rate-limited

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

FAQ

Questions about analyze_table

What does the analyze_table tool do? +

Analyze table to collect statistics information. It is categorised as a Execute tool in the Redshift 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 analyze_table? +

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

What risk level is analyze_table? +

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

Can I rate-limit analyze_table? +

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

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

analyze_table is provided by the Redshift MCP Server MCP server (moonlight-cl/redshift-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.