Low Risk

get_table_stats

Get table statistics (rows, vacuum/analyze, scan counts).

How to control get_table_stats ↓

What get_table_stats does on PostgreSQL SSH MCP Server

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

Low Risk

Why get_table_stats needs a policy

This tool queries table metadata and statistics—row counts, vacuum/analyze history, and scan counts—all of which are informational outputs with no side effects. It does not execute arbitrary queries (Execute), modify data (Write), delete data (Destructive), or move money (Financial).

From the tool's definition Tool name 'get_table_stats' and description 'Get table statistics (rows, vacuum/analyze, scan counts)' indicates retrieval of metadata and operational statistics without modification.

Documented attack patterns abuse exactly the kind of access get_table_stats gives an agent:

How to control get_table_stats

PolicyLayer is an MCP gateway — it sits between your AI agents and PostgreSQL SSH MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_table_stats:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_table_stats": {}
  }
}

get_table_stats is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register PostgreSQL SSH MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_table_stats

What does the get_table_stats tool do? +

Get table statistics (rows, vacuum/analyze, scan counts). It is categorised as a Read tool in the PostgreSQL SSH MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_table_stats? +

Register the PostgreSQL SSH MCP Server 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 PostgreSQL SSH MCP Server. 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 PostgreSQL SSH MCP Server MCP server (zlash65/postgresql-ssh-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every PostgreSQL SSH MCP Server tool call.

Start from PostgreSQL SSH MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

12 PostgreSQL SSH MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.