Delete rows from a table matching a WHERE condition. REQUIRES the
AI agents call deleteRows 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.
Deletion of database rows is irreversible and permanently destroys data. Even with a WHERE condition limiting scope, this tool can cause significant data loss if misused by an AI agent (e.g., incorrect condition logic, wrong table, overly broad filtering). In a production PostgreSQL environment, this represents maximum risk.
From the tool's definition Tool name is 'deleteRows' and description states 'Delete rows from a table matching a WHERE condition.' The verb 'delete' combined with irreversible data removal from a table is the defining characteristic of destructive operations.
Attacks that exploit this kind of access
Delete rows from a table matching a WHERE condition. REQUIRES the. 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 deleteRows: 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.
deleteRows 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 deleteRows 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 deleteRows. 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.
deleteRows is provided by the Postgresql MCP server (vnikhilbuddhavarapu/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 →