bulk_delete_by_criteria

THE RISK

Critical Risk

Why bulk_delete_by_criteria needs a policy

Bulk deletion operations are irreversible and constitute the most severe class of data/resource modification. In an infrastructure-as-code context where this tool operates on CloudFormation templates or deployed resources, deleting 'by criteria' could wipe entire infrastructure stacks without undo capability. This meets the Destructive category definition.

From the tool's definition Tool name 'bulk_delete_by_criteria' directly indicates bulk deletion based on criteria; combined with the IaC/CloudFormation context (infrastructure management), this tool would delete infrastructure resources irreversibly at scale.

Risk signalsBulk/mass operation — affects multiple targets

Documented attack patterns abuse exactly the kind of access bulk_delete_by_criteria gives an agent:

POLICY

How to control bulk_delete_by_criteria

PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Infrastructure as Code MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for bulk_delete_by_criteria:

policy.json

{
  "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.

Create a free account and register AWS Infrastructure as Code MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More AWS Infrastructure as Code MCP Server tools

Destructive cache_delete Delete a value from the cache. Destructive cache_delete_many Delete multiple values from the cache. Destructive cache_delete_multi Delete multiple values from the cache (alias for delete_many). Destructive delete delete Destructive delete_access_key delete_access_key Destructive delete_agent_runtime delete_agent_runtime Destructive delete_agent_runtime_endpoint delete_agent_runtime_endpoint Destructive delete_app delete_app

All 805 AWS Infrastructure as Code MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in AWS Infrastructure as Code MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about bulk_delete_by_criteria

What does the bulk_delete_by_criteria tool do? +

bulk_delete_by_criteria. It is categorised as a Destructive tool in the AWS Infrastructure as Code MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on bulk_delete_by_criteria? +

Register the AWS Infrastructure as Code 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 Infrastructure as Code MCP Server. Nothing to install.

What risk level is bulk_delete_by_criteria? +

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.

Can I rate-limit bulk_delete_by_criteria? +

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.

How do I block bulk_delete_by_criteria completely? +

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.

What MCP server provides bulk_delete_by_criteria? +

bulk_delete_by_criteria is provided by the AWS Infrastructure as Code MCP Server MCP server (awslabs.aws-iac-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every AWS Infrastructure as Code MCP Server tool call.

Start from AWS Infrastructure as Code MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →