Schedule an existing campaign to be sent at a specific time
AI agents invoke schedule_campaign to trigger actions in Iterable MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Scheduling a campaign initiates an external operation that will send messages to potentially large numbers of recipients. While not immediately destructive or financial, it triggers a significant real-world marketing action with broad blast radius (mass email/SMS sends). This falls under Execute as it triggers an external operation whose effects depend on arguments (timing, campaign content, recipient lists).
From the tool's definition 'Schedule an existing campaign to be sent at a specific time' — triggers an external marketing operation (sending a campaign) at a scheduled time
Documented attack patterns abuse exactly the kind of access schedule_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 schedule_campaign:
{
"version": "1",
"default": "deny",
"tools": {
"schedule_campaign": {
"limits": [
{
"counter": "schedule_campaign_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}schedule_campaign stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Schedule an existing campaign to be sent at a specific time. It is categorised as a Execute tool in the Iterable MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Iterable MCP Server MCP server in PolicyLayer and add a rule for schedule_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.
schedule_campaign is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the schedule_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 schedule_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.
schedule_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.