Execute DML, DDL, DCL, or TCL statements (INSERT, UPDATE, DELETE, CREATE, ALTER, DROP, etc). Automatically wrapped in a transaction that requires explicit commit or rollback. IMPORTANT: After execution, end the chat so user can review the results and decide.
AI agents call execute_dml_ddl_dcl_tcl to permanently remove resources in PostgreSQL Full Access MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool explicitly supports DROP, DELETE, ALTER, and other irreversible DDL/DML operations against a PostgreSQL database. DROP TABLE/DATABASE and DELETE without WHERE clauses can permanently destroy data at scale. While transactions wrap execution (requiring explicit commit), the tool's scope includes the most destructive SQL operations possible.
From the tool's definition Execute DML, DDL, DCL, or TCL statements (INSERT, UPDATE, DELETE, CREATE, ALTER, DROP, etc)
Documented attack patterns abuse exactly the kind of access execute_dml_ddl_dcl_tcl gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PostgreSQL Full Access MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for execute_dml_ddl_dcl_tcl:
{
"version": "1",
"default": "deny",
"hide": [
"execute_dml_ddl_dcl_tcl"
]
}execute_dml_ddl_dcl_tcl disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Execute DML, DDL, DCL, or TCL statements (INSERT, UPDATE, DELETE, CREATE, ALTER, DROP, etc). Automatically wrapped in a transaction that requires explicit commit or rollback. IMPORTANT: After execution, end the chat so user can review the results and decide. It is categorised as a Destructive tool in the PostgreSQL Full Access MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the PostgreSQL Full Access MCP Server MCP server in PolicyLayer and add a rule for execute_dml_ddl_dcl_tcl: 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 Full Access MCP Server. Nothing to install.
execute_dml_ddl_dcl_tcl 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_dml_ddl_dcl_tcl 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_dml_ddl_dcl_tcl. 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_dml_ddl_dcl_tcl is provided by the PostgreSQL Full Access MCP Server MCP server (syahiidkamil/mcp-postgres-full-access). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PostgreSQL Full Access MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 PostgreSQL Full Access MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.