Delete rows/records from a PostgreSQL table that match specified conditions. Use this tool to remove data from your database tables. Example: Delete all inactive users or users who haven
AI agents call delete_entry to permanently remove resources in PostgreSQL MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes records from database tables based on specified conditions. Deletions cannot be undone without backups or transaction rollback. The tool description clearly states its purpose is to 'remove data' from tables, which is a destructive operation.
From the tool's definition Tool name 'delete_entry' and description 'Delete rows/records from a PostgreSQL table that match specified conditions' and 'remove data from your database tables' explicitly perform irreversible deletion of data.
Documented attack patterns abuse exactly the kind of access delete_entry gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PostgreSQL MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_entry:
{
"version": "1",
"default": "deny",
"hide": [
"delete_entry"
]
}delete_entry 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.
Delete rows/records from a PostgreSQL table that match specified conditions. Use this tool to remove data from your database tables. Example: Delete all inactive users or users who haven. It is categorised as a Destructive tool in the PostgreSQL MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for delete_entry: 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 MCP Server. Nothing to install.
delete_entry 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 delete_entry 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 delete_entry. 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.
delete_entry is provided by the PostgreSQL MCP Server MCP server (vignesh-codes/ai-agents-mcp-pg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PostgreSQL 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.
6 PostgreSQL MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.