High-risk tools in Postgres Mcp Legacy
10 of the 60 tools in Postgres Mcp Legacy are classified as high risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at high risk
-
geo_transformExecuteTransform geometries between coordinate systems (requires PostGIS)
-
vector_performanceExecuteVector query optimization and performance benchmarking (requires pgvector)
-
geo_clusterExecuteSpatial clustering using distance-based grouping (requires PostGIS)
-
geo_index_optimizeExecuteOptimize spatial indexes (GIST/BRIN/SP-GIST) for performance (requires PostGIS)
-
json_normalizeExecuteNormalize Python-style JSON to valid JSON format
-
json_queryExecuteComplex JSON filtering and aggregation using JSONPath
-
vector_clusterExecuteK-means clustering for vector data (requires implementation)
-
vector_embedExecuteGenerate embeddings for text data (requires pgvector extension and API integration)
-
vector_index_optimizeExecuteOptimize vector indexes (HNSW/IVFFlat) for performance (requires pgvector)
-
backup_schedule_optimizeExecuteOptimize backup schedule based on database characteristics
Attacks that target this class
High-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.