analyze_table_bloat

A read tool on the Mcpg MCP server.

SERVERMcpg SOURCEpypi:mcpg

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/io-github-devopam-mcpg/analyze-table-bloat.md

WHAT IT DOES

What analyze_table_bloat does on Mcpg

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

RISK

Why analyze_table_bloat is rated Low

This tool appears to analyze table bloat statistics in PostgreSQL, which is a diagnostic operation that retrieves metadata about table fragmentation without modifying any data. It falls squarely in the Read category as a data inspection tool. Confidence is moderate (0.7) rather than high because the description is empty, requiring inference from the tool name and sibling context alone.

From the tool's definition Tool name is 'analyze_table_bloat' which indicates analysis/inspection of table metadata. The 'analyze_' prefix is consistent with other diagnostic tools on the server (analyze_distance_metric, analyze_query_plan, analyze_lock_hotspots, etc.), all of which…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs analyze_table_bloat safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcpg, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For analyze_table_bloat, this is the rule to start with:

analyze_table_bloat Allowed

analyze_table_bloat is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "analyze_table_bloat": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcpg, apply this rule, and every analyze_table_bloat call is checked against it from then on.

FAQ

Questions about analyze_table_bloat

What does the analyze_table_bloat tool do? +

analyze_table_bloat is a read tool on the Mcpg MCP server. It is categorised as a Read tool in the Mcpg MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on analyze_table_bloat? +

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

What risk level is analyze_table_bloat? +

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

Can I rate-limit analyze_table_bloat? +

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

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

analyze_table_bloat is provided by the Mcpg MCP server (pypi:mcpg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcpg, and thousands of servers like it.

This server

All 252 Mcpg tools →

Across the catalogue

analyze_devtools_anomalies on Percepta MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →