get_database_stats

Get database statistics and metadata.

SERVERPostgreSQL MCP Server SOURCEaadarshjain/postgres-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/aadarshjain-postgres-mcp-server/get-database-stats.md

WHAT IT DOES

What get_database_stats does on PostgreSQL MCP Server

AI agents call get_database_stats 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 get_database_stats is rated Low

This tool only reads and returns statistical and metadata information about the database. It has no side effects, does not execute queries, does not modify data, and does not trigger external operations. The blast radius of misuse is minimal — an AI agent could only learn about database structure and statistics, posing no risk of data loss, corruption, or unauthorized changes.

From the tool's definition Tool name is 'get_database_stats' and description states it retrieves 'database statistics and metadata' — purely informational retrieval with no modification, deletion, or execution capabilities.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_database_stats 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 get_database_stats, this is the rule to start with:

get_database_stats Allowed

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

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 get_database_stats call is checked against it from then on.

FAQ

Questions about get_database_stats

What does the get_database_stats tool do? +

Get database statistics and metadata. 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 get_database_stats? +

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

What risk level is get_database_stats? +

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

Can I rate-limit get_database_stats? +

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

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

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

KEEP EXPLORING

What get_database_stats does on PostgreSQL MCP Server

Why get_database_stats is rated Low

The rule that runs get_database_stats safely

Questions about get_database_stats

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