campaign_bulk_delete_catalog_ad_items

WHAT IT DOES

What campaign_bulk_delete_catalog_ad_items does on AdButler

AI agents call campaign_bulk_delete_catalog_ad_items to permanently remove resources in AdButler — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Parameter	Type	Required	Description
`items`	array	Yes	Array of catalog ad item IDs to delete
`campaign_id`	number	Yes	Campaign ID

Parameters from the server's own tool schema.

THE RISK

Critical Risk

Why campaign_bulk_delete_catalog_ad_items needs a policy

Bulk delete operations are inherently destructive—they permanently remove data without reversibility. The bulk nature amplifies the blast radius: an AI agent misunderstanding the campaign context or receiving incorrect arguments could delete large volumes of ad items, causing significant business disruption and data loss. This cannot be undone, making it the most severe category applicable.

From the tool's definition Tool name explicitly contains 'bulk_delete' and description states 'Bulk delete catalog ad items from a campaign'. The 'delete' operation is irreversible and affects multiple items simultaneously ('bulk').

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

POLICY

How to control campaign_bulk_delete_catalog_ad_items

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

policy.json

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

campaign_bulk_delete_catalog_ad_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 AdButler — 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 AdButler tools

Financial create_contract_payment Create a new payment for a contract Destructive cancel_signature_request Cancel a signature request Destructive delete_advertiser Delete an advertiser Destructive delete_archived_campaign Permanently delete an archived standard campaign Destructive delete_archived_channel Permanently delete an archived channel Destructive delete_archived_contract Permanently delete an archived contract Destructive delete_audience Delete an audience from a user database Destructive delete_audio_creative Delete an audio creative

All 622 AdButler 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 AdButler → 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 campaign_bulk_delete_catalog_ad_items

What does the campaign_bulk_delete_catalog_ad_items tool do? +

Bulk delete catalog ad items from a campaign. It is categorised as a Destructive tool in the AdButler MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does campaign_bulk_delete_catalog_ad_items accept? +

campaign_bulk_delete_catalog_ad_items accepts 2 parameters: items, campaign_id. Required: items, campaign_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on campaign_bulk_delete_catalog_ad_items? +

Register the AdButler MCP server in PolicyLayer and add a rule for campaign_bulk_delete_catalog_ad_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 AdButler. Nothing to install.

What risk level is campaign_bulk_delete_catalog_ad_items? +

campaign_bulk_delete_catalog_ad_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 campaign_bulk_delete_catalog_ad_items? +

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

Set action: deny in the PolicyLayer policy for campaign_bulk_delete_catalog_ad_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 campaign_bulk_delete_catalog_ad_items? +

campaign_bulk_delete_catalog_ad_items is provided by the AdButler MCP server (adbutler/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.