// SCAN REPORT

MCP Server Project

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

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

Last updated: 4 Jul 2026

1 can modify or destroy data

3 read-only

4 tools total

Community server · catalogue entry verified 04/07/2026

How to control MCP Server Project ↓

TOOL MAP

What MCP Server Project exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous MCP Server Project tools

Execute · Critical postgres_execute_query A tool that executes arbitrary PostgreSQL queries can run any SQL command including SELECT, INSERT, UPDATE, DELETE, or DROP statements.

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

POLICY

How to control MCP Server Project

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

Cap read operations

{
  "postgres_describe_table": {
    "limits": [
      {
        "counter": "postgres_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 MCP Server Project — 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 MCP SERVER PROJECT →

Instant setup, no code required.

FULL CATALOGUE

All 4 MCP Server Project tools

EXECUTE 1 tools

Execute postgres_execute_query postgres_execute_query

READ 3 tools

Read postgres_describe_table postgres_describe_table Read postgres_get_table_sample postgres_get_table_sample Read postgres_list_tables postgres_list_tables

EXPLORE

Related servers

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

FAQ

Questions about MCP Server Project

Is the MCP Server Project MCP server safe to use without restrictions? +

The MCP Server Project server is primarily read-only with 3 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 MCP Server Project MCP server expose? +

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

How do I enforce a policy on MCP Server Project? +

Register the MCP Server Project 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 MCP Server Project tool call.

Deterministic rules across all 4 MCP Server Project tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MCP SERVER PROJECT →

Instant setup, no code required.

4 MCP Server Project tools catalogued and risk-classified — across an index of 43,000+ MCP servers.