Create a new blast campaign from an existing template. The campaign is created without being scheduled. Use schedule_campaign to schedule it for delivery.
AI agents use create_blast_campaign to create or update resources in Iterable MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Iterable MCP Server environment.
This tool creates a marketing campaign object, which is a Write operation. It modifies the marketing platform's state by adding a new campaign, but the action is reversible through archive or cancel operations. While campaigns can impact users when delivered, the creation itself has no immediate side effects—delivery requires a separate 'schedule_campaign' call.
From the tool's definition Tool description states 'Create a new blast campaign from an existing template.' The verb 'Create' indicates data creation.
Documented attack patterns abuse exactly the kind of access create_blast_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 create_blast_campaign:
{
"version": "1",
"default": "deny",
"tools": {
"create_blast_campaign": {
"limits": [
{
"counter": "create_blast_campaign_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_blast_campaign stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new blast campaign from an existing template. The campaign is created without being scheduled. Use schedule_campaign to schedule it for delivery. It is categorised as a Write tool in the Iterable MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Iterable MCP Server MCP server in PolicyLayer and add a rule for create_blast_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.
create_blast_campaign is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_blast_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 create_blast_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.
create_blast_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.