trigger_campaign

THE RISK

High Risk

Why trigger_campaign needs a policy

Triggering a campaign to send messages constitutes execution of an external operation with immediate, user-facing side effects. While not destructive or financial in nature, the blast radius is significant: a misconfigured or unintended campaign trigger could send unsolicited communications to large user populations, damage reputation, and violate regulations (e.g., CAN-SPAM).

From the tool's definition Tool description states 'Trigger a campaign to send' — this executes an external operation (sending a marketing campaign) whose effects depend on the specified lists argument.

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

POLICY

How to control trigger_campaign

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 trigger_campaign:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "trigger_campaign": {
      "limits": [
        {
          "counter": "trigger_campaign_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

trigger_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.

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.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Iterable MCP Server tools

Destructive bulk_delete_catalog_items Bulk delete catalog items by their IDs 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

All 78 Iterable MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Iterable MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-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.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about trigger_campaign

What does the trigger_campaign tool do? +

Trigger a campaign to send to specified lists. 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.

How do I enforce a policy on trigger_campaign? +

Register the Iterable MCP Server MCP server in PolicyLayer and add a rule for trigger_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.

What risk level is trigger_campaign? +

trigger_campaign is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit trigger_campaign? +

Yes. Add a rate_limit block to the trigger_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.

How do I block trigger_campaign completely? +

Set action: deny in the PolicyLayer policy for trigger_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.

What MCP server provides trigger_campaign? +

trigger_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.

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 →