Get detailed statistics for a specific table including live/dead row counts, dead row ratio, last vacuum/analyze timestamps, and modification count since last analyze. Useful for monitoring table health.
AI agents call getTableStats to retrieve information from Postgresql without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries PostgreSQL system catalogs (pg_stat_user_tables or similar) to retrieve table metadata and statistics. It performs no write, delete, execute, or financial operations—it only reads and reports statistics. Even in a context where other tools on the server can execute destructive operations (deleteRows, dropIndex, executeDDL), this specific tool is purely informational.
From the tool's definition Tool retrieves 'detailed statistics' including 'live/dead row counts', 'timestamps', and 'modification count' with no description of modification or deletion of data. The verb 'Get' and phrase 'Useful for monitoring' indicate a diagnostic query-only operation.
Attacks that exploit this kind of access
Get detailed statistics for a specific table including live/dead row counts, dead row ratio, last vacuum/analyze timestamps, and modification count since last analyze. Useful for monitoring table health. It is categorised as a Read tool in the Postgresql MCP Server, which means it retrieves data without modifying state.
Register the Postgresql MCP server in PolicyLayer and add a rule for getTableStats: 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.
getTableStats is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getTableStats 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.
Set action: deny in the PolicyLayer policy for getTableStats. 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.
getTableStats 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →