Delete rows from a table based on specified conditions
AI agents call delete_data to permanently remove resources in MCP PostgreSQL Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Despite the server's stated purpose of providing 'secure read-only access,' this tool directly deletes rows from a database table, which is an irreversible operation that cannot be undone without separate backup/restore procedures. This is a destructive action with potentially significant blast radius if an AI agent misuses the condition specification.
From the tool's definition Tool name is 'delete_data' with description 'Delete rows from a table based on specified conditions.' The word 'Delete' combined with the irreversible nature of row deletion from a database makes this clearly a destructive operation.
Attacks that exploit this kind of access
Delete rows from a table based on specified conditions. It is categorised as a Destructive tool in the MCP PostgreSQL Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP PostgreSQL Server MCP server in PolicyLayer and add a rule for delete_data: 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 MCP PostgreSQL Server. Nothing to install.
delete_data 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_data 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_data. 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_data is provided by the MCP PostgreSQL Server MCP server (kristofer84/mcp-postgres). 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 →