get_table_stats

Get statistics for a table: estimated row count (from pg_stat), live/dead tuples, last vacuum/analyze times, and total disk size.

Server Mcp Postgres Query lordbasilaiassistant-sudo/mcp-postgres-query
Category Read
Risk class Low
Parameters 00 required

What get_table_stats does on Mcp Postgres Query

AI agents call get_table_stats to retrieve information from Mcp Postgres Query without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_table_stats needs a policy

This tool only queries PostgreSQL's built-in statistics tables to return informational metrics. It performs no writes, deletes, or execution of arbitrary code—only retrieves pre-computed statistics that are already available to any database user. The blast radius of misuse is minimal; an attacker could only learn about table sizes and maintenance history, not access or modify actual data.

From the tool's definition The tool retrieves statistics ('Get statistics for a table') including row counts, tuple counts, maintenance timestamps, and disk size from PostgreSQL system catalogs (pg_stat). These are read-only queries with no modification of data or schema.

Questions about get_table_stats

What does the get_table_stats tool do? +

Get statistics for a table: estimated row count (from pg_stat), live/dead tuples, last vacuum/analyze times, and total disk size. It is categorised as a Read tool in the Mcp Postgres Query MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_table_stats? +

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

What risk level is get_table_stats? +

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

Can I rate-limit get_table_stats? +

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

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

get_table_stats is provided by the Mcp Postgres Query MCP server (lordbasilaiassistant-sudo/mcp-postgres-query). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.