// SCAN REPORT

Iterable MCP Server

78 tools. 43 can modify or destroy data without limits.

12 destructive tools with no built-in limits. Policy required.

Last updated: 12 Jun 2026

43 can modify or destroy data

35 read-only

78 tools total

Community server · catalogue entry verified 12/06/2026

How to control Iterable MCP Server ↓

TOOL MAP

What Iterable MCP Server exposes to your agents

Read (35) Write / Execute (31) Destructive / Financial (12)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Iterable MCP Server tools

Destructive · High bulk_delete_catalog_items This tool permanently removes data from the Iterable catalog without the ability to undo the action. Destructive · High delete_user_by_user_id This tool permanently removes user records from the Iterable platform. Destructive · High cancel_campaign Canceling a campaign is a destructive operation that irreversibly halts a scheduled or recurring marketing initiative. Destructive · Medium cancel_export_job Cancelling an export job stops it permanently; the job cannot be resumed once cancelled, making it an irreversible operation.

43 of Iterable MCP Server's 78 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Iterable MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Iterable MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "bulk_delete_catalog_items": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "deactivate_triggered_campaign": {
    "limits": [
      {
        "counter": "deactivate_triggered_campaign_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_available_export_data_types": {
    "limits": [
      {
        "counter": "get_available_export_data_types_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Iterable MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON ITERABLE →

Free to start. No card required.

FULL CATALOGUE

All 78 Iterable MCP Server tools

DESTRUCTIVE 12 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 Destructive delete_user_by_email Delete a user by email address (asynchronous - does not prevent future data collection) Destructive delete_user_by_user_id Delete a user by user ID (asynchronous - does not prevent future data collection, deletes all users with same Destructive abort_campaign Abort a campaign that is currently running Destructive archive_campaigns Archive one or more campaigns. Scheduled/recurring campaigns will be cancelled, running campaigns will be abor

EXECUTE 6 tools

Execute start_export_job Start a data export job that processes as a background job. Use Execute trigger_campaign Trigger a campaign to send to specified lists Execute trigger_journey Trigger a journey (workflow) for a user Execute activate_triggered_campaign Activate a triggered campaign (requires API triggered campaign activation enabled) Execute schedule_campaign Schedule an existing campaign to be sent at a specific time Execute send_campaign Send an existing scheduled campaign immediately

WRITE 25 tools

Write deactivate_triggered_campaign Deactivate a triggered campaign (requires API triggered campaign deactivation enabled) Write subscribe_to_list Subscribe users to a specific list Write subscribe_user_by_email Subscribe a user to a subscription group by email Write subscribe_user_by_userid Subscribe a user to a subscription group by userId Write track_bulk_events Track multiple events in a single request for better performance Write track_event Track a custom event for a user Write unsubscribe_from_list Unsubscribe users from a specific list Write unsubscribe_user_by_email Unsubscribe a user from a subscription group by email Write unsubscribe_user_by_userid Unsubscribe a user from a subscription group by userId Write bulk_update_subscriptions Subscribe or unsubscribe multiple users to/from a subscription group Write bulk_update_users Update multiple users at once Write create_blast_campaign Create a new blast campaign from an existing template. The campaign is created without being scheduled. Use sc Write create_catalog Create a new catalog Write create_list Create a new user list Write create_snippet Create a new snippet with Handlebars templating support Write create_triggered_campaign Create a new triggered campaign from an existing template. The campaign is created in Ready state and must be Write partial_update_catalog_item Partial update (PATCH) a catalog item - updates only specified fields Write replace_catalog_item Replace (PUT) a catalog item - replaces the entire item with new value Write update_catalog_field_mappings Update catalog field mappings (data types). Valid types: boolean, date, geo_location, long, double, object, an Write update_catalog_items Update catalog items Write update_email Update a user Write update_snippet Update a snippet by ID (numeric) or name (string) Write update_user Update user profile information (accepts email OR userId in params) Write update_user_subscriptions Update user subscriptions (IMPORTANT: overwrites existing data for any non-null fields specified) Write update_webhook Update a webhook configuration

READ 35 tools

Read get_available_export_data_types Get the list of all available export data types that can be used with start_export_job. Returns an array of da Read get_campaign Get detailed information about a specific campaign Read get_campaign_metrics Get campaign performance metrics. Requires a date range. Always use the narrowest window possible for performa Read get_campaigns Retrieve campaigns Read get_catalog_field_mappings Get field mappings and data types for a catalog Read get_catalog_item Get a specific catalog item by ID Read get_catalog_items Get items from a catalog with optional pagination and sorting Read get_catalogs Get list of all catalogs with optional pagination Read get_channels Get all available communication channels (email, SMS, push, etc.) Read get_child_campaigns Get child campaigns generated by a recurring campaign Read get_embedded_messages Get embedded messages for a user, grouped by placement ID Read get_experiment Get detailed information about a specific experiment by ID, including variants summary and constraints Read get_experiment_metrics Get experiment metrics for A/B testing analysis (currently supports email experiments only) Read get_experiment_variants Get variant content for an experiment, including subject lines, preheaders, HTML source, and plain text Read get_export_files Get the job status and download URLs for files from a completed export job. Files are added to the list as the Read get_export_jobs Get a list of recent export jobs for the current project. Jobs can be filtered by state (enqueued, queued, run Read get_in_app_messages Get in-app messages for a user Read get_journeys Get journeys (workflows) with optional pagination and state filtering Read get_list_preview_users Preview users in a list (up to 5000 users) Read get_list_size Get the count of users in a specific list Read get_list_users Get users in a specific list Read get_lists Retrieve user lists Read get_message_types Get all message types within the project for use in templates Read get_sent_messages Get messages sent to a specific user with optional filtering Read get_snippet Get a snippet by ID (numeric) or name (string) Read get_snippets Get all snippets for the current project Read get_template_by_client_id Get template by client template ID Read get_templates Retrieve templates Read get_user_by_email Get user profile information by email address Read get_user_by_user_id Get user profile information by user ID Read get_user_events_by_email Get event history for a user by email address Read get_user_events_by_user_id Get event history for a user by user ID Read get_user_fields Get all user profile field definitions and their types Read get_webhooks Get all webhooks for the project Read list_experiments List experiments with optional filtering by campaign, status, and date range. Supports pagination.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Iterable MCP Server

Can an AI agent delete data through the Iterable MCP Server MCP server? +

Yes. The Iterable MCP Server server exposes 12 destructive tools including bulk_delete_catalog_items, cancel_campaign, cancel_export_job. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Iterable MCP Server? +

The Iterable MCP Server server has 25 write tools including deactivate_triggered_campaign, subscribe_to_list, subscribe_user_by_email. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Iterable MCP Server.

How many tools does the Iterable MCP Server MCP server expose? +

78 tools across 4 categories: Destructive, Execute, Read, Write. 35 are read-only. 43 can modify, create, or delete data.

How do I enforce a policy on Iterable MCP Server? +

Register the Iterable MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Iterable MCP Server tool call.

Deterministic rules across all 78 Iterable MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON ITERABLE →

Free to start. No card required.

78 Iterable MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.