High-risk tools in PostgreSQL Database Management Server
3 of the 18 tools in PostgreSQL Database Management Server 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
-
pg_execute_mutationExecute 3/5Execute data modification operations (INSERT/UPDATE/DELETE/UPSERT) - operation="insert/update/delete/upsert" with table and data. Examples: operation="insert", table="users", da...
-
pg_execute_queryExecute 4/5Execute SELECT queries and data retrieval operations - operation="select/count/exists" with query and optional parameters. Examples: operation="select", query="SELECT * FROM use...
-
pg_execute_sqlExecute 4/5Execute arbitrary SQL statements - sql="ANY_VALID_SQL" with optional parameters and transaction support. Examples: sql="CREATE INDEX ...", sql="WITH complex_cte AS (...) SELECT ...
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.
More on PostgreSQL Database Management Server
Enforce policy on PostgreSQL Database Management Server
One command generates a policy scaffold for every server in your MCP config.
npx -y @policylayer/intercept init