Execute a write SQL statement (INSERT, UPDATE, DELETE, TRUNCATE, CREATE, DROP). Returns rows affected.
AI agents call execute to permanently remove resources in Postgresql — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool explicitly supports TRUNCATE and DROP statements, which are irreversible destructive operations. DROP can permanently delete entire tables or databases, and TRUNCATE removes all rows without the ability to roll back in many contexts. Combined with full read-write SQL access on any PostgreSQL instance, misuse could cause catastrophic and unrecoverable data loss.
From the tool's definition Execute a write SQL statement (INSERT, UPDATE, DELETE, TRUNCATE, CREATE, DROP)
Attacks that exploit this kind of access
Execute a write SQL statement (INSERT, UPDATE, DELETE, TRUNCATE, CREATE, DROP). Returns rows affected. It is categorised as a Destructive tool in the Postgresql MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Postgresql MCP server in PolicyLayer and add a rule for execute: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Postgresql. Nothing to install.
execute is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the execute rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for execute. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
execute is provided by the Postgresql MCP server (sarmadparvez/postgresql-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →