pg_table_sizes

Get sizes of all tables with indexes and total.

SERVERPostgreSQL MCP Server SOURCE@neverinfamous/postgres-mcp

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-neverinfamous-postgres-mcp/pg-table-sizes.md

WHAT IT DOES

What pg_table_sizes does on PostgreSQL MCP Server

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

RISK

Why pg_table_sizes is rated Low

This tool retrieves storage size information about PostgreSQL tables and their indexes. It performs a query operation with no side effects—no data is created, modified, deleted, or executed. The severity is low because even if an AI agent runs this tool excessively, it only reads metadata and cannot harm the database or system.

From the tool's definition Tool name 'pg_table_sizes' and description 'Get sizes of all tables with indexes and total' indicate a read-only query operation that retrieves and reports on table metadata without modifying, executing code, or deleting data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pg_table_sizes safely

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

pg_table_sizes Allowed

pg_table_sizes 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": {
    "pg_table_sizes": {}
  }
}

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

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

FAQ

Questions about pg_table_sizes

What does the pg_table_sizes tool do? +

Get sizes of all tables with indexes and total. It is categorised as a Read tool in the PostgreSQL MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pg_table_sizes? +

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

What risk level is pg_table_sizes? +

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

Can I rate-limit pg_table_sizes? +

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

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

pg_table_sizes is provided by the PostgreSQL MCP Server MCP server (@neverinfamous/postgres-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

What pg_table_sizes does on PostgreSQL MCP Server

Why pg_table_sizes is rated Low

The rule that runs pg_table_sizes safely

Questions about pg_table_sizes

More on PostgreSQL MCP Server, and thousands of servers like it.