Cancel a scheduled or recurring campaign
AI agents call cancel_campaign to permanently remove resources in Iterable MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Canceling a campaign is a destructive operation that irreversibly halts a scheduled or recurring marketing initiative. Once canceled, the campaign state cannot be simply restored without manual recreation. This is more severe than Write (which is reversible modification) and qualifies as Destructive.
From the tool's definition Tool name is 'cancel_campaign' and description states 'Cancel a scheduled or recurring campaign'. Cancellation of a campaign is an irreversible action that terminates planned marketing operations and cannot be undone.
Documented attack patterns abuse exactly the kind of access cancel_campaign gives an agent:
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 cancel_campaign:
{
"version": "1",
"default": "deny",
"hide": [
"cancel_campaign"
]
} cancel_campaign 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.
Cancel a scheduled or recurring campaign. 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.
Register the Iterable MCP Server MCP server in PolicyLayer and add a rule for cancel_campaign: 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.
cancel_campaign 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 cancel_campaign 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 cancel_campaign. 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.
cancel_campaign 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.
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.
Free to start. No card required.
78 Iterable MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.