# get_database_stats

Get database statistics and metadata.

Agent View of the PolicyLayer registry record for `get_database_stats`. HTML page: https://policylayer.com/tools/aadarshjain-postgres-mcp-server/get-database-stats

## Facts

- Tool: `get_database_stats`
- Server: PostgreSQL MCP Server (`aadarshjain/postgres-mcp-server`) — https://policylayer.com/tools/aadarshjain-postgres-mcp-server.md
- Homepage: https://github.com/aadarshjain/postgres-mcp-server
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_database_stats",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches PostgreSQL MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_database_stats": {}
  }
}
```

## Other tools on PostgreSQL MCP Server (4)

- `execute_query` — Execute — https://policylayer.com/tools/aadarshjain-postgres-mcp-server/execute-query.md
- `filter_instances` — Read — https://policylayer.com/tools/aadarshjain-postgres-mcp-server/filter-instances.md
- `get_table_schema` — Read — https://policylayer.com/tools/aadarshjain-postgres-mcp-server/get-table-schema.md
- `list_tables` — Read — https://policylayer.com/tools/aadarshjain-postgres-mcp-server/list-tables.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=aadarshjain-postgres-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/aadarshjain-postgres-mcp-server