New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

PostgreSQL_get_estimated_row_counts

Get estimated row counts for all tables using statistics (faster than COUNT(*)).

SERVERPostgres SOURCEmukul975/postgres-mcp-server
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/mukul975-postgres-mcp-server/postgresql-get-estimated-row-counts.md

What PostgreSQL_get_estimated_row_counts does on Postgres

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

Why PostgreSQL_get_estimated_row_counts is rated Low

This tool queries PostgreSQL statistics to retrieve estimated row counts. It performs no data modifications, deletions, or external operations. The word 'estimated' and 'statistics' confirm it reads pre-computed metadata rather than executing potentially expensive operations. This is a standard read operation with minimal blast radius if misused—worst case, an agent repeatedly calls it, causing minor I/O overhead.

From the tool's definition Tool description states it 'Get estimated row counts for all tables using statistics', which retrieves data without modification. The method uses statistical estimates rather than executing aggregate queries, making it a non-invasive read operation.

Questions about PostgreSQL_get_estimated_row_counts

What does the PostgreSQL_get_estimated_row_counts tool do? +

Get estimated row counts for all tables using statistics (faster than COUNT(*)). It is categorised as a Read tool in the Postgres MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on PostgreSQL_get_estimated_row_counts? +

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

What risk level is PostgreSQL_get_estimated_row_counts? +

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

Can I rate-limit PostgreSQL_get_estimated_row_counts? +

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

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

PostgreSQL_get_estimated_row_counts is provided by the Postgres MCP server (mukul975/postgres-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Postgres, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Postgres's. Pull the full record:

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.