// SCAN REPORT

Postgres Mcp Legacy

60 tools. 16 can modify or destroy data without limits.

15 write tools that can modify data. Rate limits recommended.

Last updated: 12 Jun 2026

16 can modify or destroy data

44 read-only

60 tools total

Community server · catalogue entry verified 12/06/2026

How to control Postgres Mcp Legacy ↓

TOOL MAP

What Postgres Mcp Legacy exposes to your agents

Read (44) Write / Execute (15) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Postgres Mcp Legacy tools

Execute · High geo_transform This tool performs coordinate system transformations on spatial data in PostgreSQL. Execute · High vector_performance Vector query optimization and benchmarking constitutes code execution that triggers external database operations whose effects depend on the arguments passed (which queries to optimize, benchmark parameters, etc.). Execute · Medium backup_schedule_optimize This tool triggers an optimization operation that reconfigures backup scheduling, which is an active execution of a process that changes system configuration. Execute · Medium geo_cluster This tool runs a spatial clustering operation on the database, which involves executing PostGIS geospatial functions and queries.

16 of Postgres Mcp Legacy's 60 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 Mcp Legacy

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

Rate limit write operations

{
  "alert_threshold_set": {
    "limits": [
      {
        "counter": "alert_threshold_set_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "performance_baseline": {
    "limits": [
      {
        "counter": "performance_baseline_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 Mcp Legacy — 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 MCP LEGACY →

Free to start. No card required.

FULL CATALOGUE

All 60 Postgres Mcp Legacy tools

EXECUTE 10 tools

Execute geo_transform Transform geometries between coordinate systems (requires PostGIS) Execute vector_performance Vector query optimization and performance benchmarking (requires pgvector) Execute geo_cluster Spatial clustering using distance-based grouping (requires PostGIS) Execute geo_index_optimize Optimize spatial indexes (GIST/BRIN/SP-GIST) for performance (requires PostGIS) Execute json_normalize Normalize Python-style JSON to valid JSON format Execute json_query Complex JSON filtering and aggregation using JSONPath Execute vector_cluster K-means clustering for vector data (requires implementation) Execute vector_embed Generate embeddings for text data (requires pgvector extension and API integration) Execute vector_index_optimize Optimize vector indexes (HNSW/IVFFlat) for performance (requires pgvector) Execute backup_schedule_optimize Optimize backup schedule based on database characteristics

WRITE 5 tools

Write alert_threshold_set Analyze metrics against alert thresholds Write geo_buffer Create buffer zones around geometries (requires PostGIS) Write json_insert Insert or update JSONB data with validation Write json_merge Merge JSON objects with conflict resolution strategies Write json_update Update JSON value by path, optionally creating path if missing

READ 44 tools

Read performance_baseline Establish performance baselines for critical queries Read analyze_db_health Analyzes database health. Here are the available health checks:\n Read backup_logical Generate logical backup plan with validation Read backup_physical Analyze physical backup readiness and configuration Read capacity_planning Analyze database growth and project future capacity needs Read connection_pool_optimize Analyze connection pool and provide optimization recommendations Read explain_query Explains the execution plan for a SQL query, showing how the database will execute it and provides detailed co Read fuzzy_match Find fuzzy matches using Levenshtein distance (requires fuzzystrmatch extension) Read geo_distance Calculate distance between geometries (requires PostGIS extension) Read geo_intersection Find geometric intersections (requires PostGIS) Read geo_within Point-in-polygon and geometric containment queries (requires PostGIS) Read get_object_details Show detailed information about a database object Read get_top_queries get_top_queries Read hybrid_search Hybrid search combining full-text and vector similarity (requires pgvector) Read json_diff Compare two JSON structures and return differences Read json_security_scan Scan JSON data for potential security issues Read json_validate_path Validate JSONPath expression with security checks Read jsonb_index_suggest Suggest indexes for JSONB columns based on usage patterns Read jsonb_stats Analyze JSON structure and generate statistics Read list_objects List objects in a schema Read list_schemas List all schemas in the database Read monitor_real_time Monitor real-time database performance metrics Read partition_strategy_suggest Suggest partitioning strategy for large tables Read query_plan_compare Compare execution plans of two queries with cost analysis Read regex_extract_all Extract all pattern matches with capture groups using regex Read replication_monitor Monitor replication status and lag Read resource_usage_analyze Analyze database resource usage patterns (CPU/Memory/IO) Read slow_query_analyzer Analyze slow queries with optimization suggestions (requires pg_stat_statements) Read stats_correlation Calculate correlation between two numeric columns (Pearson or Spearman) Read stats_descriptive Calculate descriptive statistics (mean, median, mode, std dev) for numeric columns Read stats_distribution Analyze data distribution with histogram and distribution fitting Read stats_hypothesis Perform hypothesis testing (t-test, z-test) Read stats_percentiles Calculate percentiles and detect outliers using IQR method Read stats_regression Calculate linear regression analysis with coefficients and R-squared Read stats_sampling Generate statistical samples from tables (random, systematic, stratified) Read stats_time_series Analyze time series data with aggregation and trend analysis Read text_search_advanced Advanced full-text search with ranking Read text_sentiment Basic sentiment analysis using keyword matching Read text_similarity Find similar text using trigram similarity (requires pg_trgm extension) Read vacuum_strategy_recommend Analyze vacuum needs and recommend vacuum strategy Read vector_search Semantic search with ranking and distance threshold (requires pgvector) Read vector_similarity Find similar vectors using cosine, L2, or inner product distance (requires pgvector) Read json_select Extract JSON data with multiple output formats Read restore_validate Validate database readiness for restore operations

OTHER 1 tools

Other vector_dimension_reduce Dimensionality reduction for vector data (requires implementation)

EXPLORE

Related servers

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

FAQ

Questions about Postgres Mcp Legacy

How do I prevent bulk modifications through Postgres Mcp Legacy? +

The Postgres Mcp Legacy server has 5 write tools including alert_threshold_set, geo_buffer, json_insert. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Postgres Mcp Legacy.

How many tools does the Postgres Mcp Legacy MCP server expose? +

60 tools across 3 categories: Execute, Read, Write. 44 are read-only. 16 can modify, create, or delete data.

How do I enforce a policy on Postgres Mcp Legacy? +

Register the Postgres Mcp Legacy 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 Mcp Legacy tool call.

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

ENFORCE POLICY ON POSTGRES MCP LEGACY →

Free to start. No card required.

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