bulk_delete_by_criteria
AI agents call bulk_delete_by_criteria to permanently remove resources in AWS Labs postgres MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Bulk deletion is irreversible and has high blast radius. Without a description to clarify scope or safeguards, the tool must be classified as Destructive. The 'bulk' modifier suggests potential for massive data loss. Confidence is lowered slightly due to empty description, but the name alone is sufficiently clear to warrant critical severity.
From the tool's definition Tool named 'bulk_delete_by_criteria' with no description provided. The name explicitly indicates bulk deletion operations based on specified criteria.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access bulk_delete_by_criteria gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Labs postgres MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for bulk_delete_by_criteria:
{
"version": "1",
"default": "deny",
"hide": [
"bulk_delete_by_criteria"
]
}bulk_delete_by_criteria 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.
bulk_delete_by_criteria. It is categorised as a Destructive tool in the AWS Labs postgres MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AWS Labs postgres MCP Server MCP server in PolicyLayer and add a rule for bulk_delete_by_criteria: 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 AWS Labs postgres MCP Server. Nothing to install.
bulk_delete_by_criteria 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 bulk_delete_by_criteria 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 bulk_delete_by_criteria. 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.
bulk_delete_by_criteria is provided by the AWS Labs postgres MCP Server MCP server (awslabs.postgres-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS Labs postgres 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.
805 AWS Labs postgres MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.