bulk_delete_catalog_items

THE RISK

Critical Risk

Why bulk_delete_catalog_items needs a policy

This tool permanently removes data from the Iterable catalog without the ability to undo the action. Bulk deletion amplifies the risk by allowing multiple items to be destroyed in a single operation. An AI agent with improper prompting or instruction injection could accidentally or maliciously delete large volumes of catalog data, causing significant business impact.

From the tool's definition Tool name is 'bulk_delete_catalog_items' and description states it will 'Bulk delete catalog items by their IDs'. The verb 'delete' combined with 'bulk' operation indicates irreversible removal of data at scale.

Risk signalsBulk/mass operation — affects multiple targets

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

POLICY

How to control bulk_delete_catalog_items

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "bulk_delete_catalog_items"
  ]
}

bulk_delete_catalog_items 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 Iterable 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 Iterable MCP Server tools

Destructive cancel_campaign Cancel a scheduled or recurring campaign Destructive cancel_export_job Cancel a queued or running export job created with Destructive delete_catalog Delete a catalog Destructive delete_catalog_item Delete a specific catalog item by ID Destructive delete_list Delete a user list Destructive delete_snippet Delete a snippet by ID (numeric) or name (string) Destructive delete_templates Delete one or more templates by ID Destructive delete_user_by_email Delete a user by email address (asynchronous - does not prevent future data collection)

All 78 Iterable 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 Iterable 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_catalog_items

What does the bulk_delete_catalog_items tool do? +

Bulk delete catalog items by their IDs. It is categorised as a Destructive tool in the Iterable 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_catalog_items? +

Register the Iterable MCP Server MCP server in PolicyLayer and add a rule for bulk_delete_catalog_items: 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 Iterable MCP Server. Nothing to install.

What risk level is bulk_delete_catalog_items? +

bulk_delete_catalog_items 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_catalog_items? +

Yes. Add a rate_limit block to the bulk_delete_catalog_items 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_catalog_items completely? +

Set action: deny in the PolicyLayer policy for bulk_delete_catalog_items. 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_catalog_items? +

bulk_delete_catalog_items is provided by the Iterable MCP Server MCP server (iterable/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 Iterable MCP Server tool call.

Start from Iterable 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 →