// SCAN REPORT

Postgres

14 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 12 Jun 2026

1 can modify or destroy data

13 read-only

14 tools total

Community server · catalogue entry verified 12/06/2026

How to control Postgres ↓

TOOL MAP

What Postgres exposes to your agents

Read (13) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Postgres tools

Execute · High execute This tool runs arbitrary INSERT, UPDATE, and DELETE SQL statements, which can modify or destroy data.

1 of Postgres's 14 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Postgres

PolicyLayer is an MCP gateway — it sits between your AI agents and Postgres, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "describe_table": {
    "limits": [
      {
        "counter": "describe_table_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Postgres — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON POSTGRES →

Free to start. No card required.

FULL CATALOGUE

All 14 Postgres tools

EXECUTE 1 tools

Execute execute Execute a write SQL statement (INSERT, UPDATE, DELETE). WARNING: This tool modifies data. Only available if AL

READ 13 tools

Read describe_table Describe the structure of a table including columns, types, and constraints. Read describe_view Get the definition and columns of a view. Read explain_query Get the execution plan for a SQL query (EXPLAIN). Read get_database_info Get database and connection information. Read list_constraints List all constraints for a table (PK, FK, UNIQUE, CHECK). Read list_functions List all functions and procedures in a schema. Read list_indexes List all indexes for a table. Read list_schemas List all schemas in the PostgreSQL database. Read list_tables List all tables in a specific schema. Read list_views List all views in a schema. Read query Execute a SQL query against the PostgreSQL database. This tool is READ-ONLY by default. Use the Read search_columns Search for columns by name across all tables. Read table_stats Get statistics for a table (row count, size, bloat).

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Postgres

Is the Postgres MCP server safe to use without restrictions? +

The Postgres server is primarily read-only with 13 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Postgres MCP server expose? +

14 tools across 2 categories: Execute, Read. 13 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on Postgres? +

Register the Postgres MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Postgres tool call.

Deterministic rules across all 14 Postgres tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON POSTGRES →

Free to start. No card required.

14 Postgres tools catalogued and risk-classified — across an index of 43,000+ MCP servers.