PostgreSQL_execute_update_query

What PostgreSQL_execute_update_query does on Postgres

AI agents invoke PostgreSQL_execute_update_query to trigger actions in Postgres. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why PostgreSQL_execute_update_query is rated High

While DELETE could argue for Destructive category, the tool's primary capability spans multiple SQL operations (UPDATE, INSERT, DELETE). UPDATE and INSERT are reversible modifications (Write), but the inclusion of DELETE—which irreversibly removes data—elevates this to Execute due to the tool's broad scope and the potential for an AI agent to issue unintended DELETE commands.

From the tool's definition Tool name and description explicitly state it executes UPDATE, INSERT, or DELETE queries. UPDATE and INSERT are data-modifying operations; DELETE is destructive. The tool permits execution of arbitrary SQL commands that modify or remove data.

The rule that runs PostgreSQL_execute_update_query safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Postgres, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For PostgreSQL_execute_update_query, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "PostgreSQL_execute_update_query": {
      "limits": [
        {
          "counter": "postgresql_execute_update_query_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about PostgreSQL_execute_update_query