Subscribe or unsubscribe multiple users to/from a subscription group
AI agents use bulk_update_subscriptions 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 or modifies data (subscription preferences) in a reversible manner—subscriptions can be toggled on or off. It does not delete data permanently, execute arbitrary code, or move money. However, the 'bulk' nature and potential for widespread impact on user communication preferences elevates severity from low to medium.
From the tool's definition Tool name 'bulk_update_subscriptions' and description 'Subscribe or unsubscribe multiple users to/from a subscription group' indicate modification of user subscription states affecting potentially hundreds or thousands of users at once.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access bulk_update_subscriptions 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 bulk_update_subscriptions:
{
"version": "1",
"default": "deny",
"tools": {
"bulk_update_subscriptions": {
"limits": [
{
"counter": "bulk_update_subscriptions_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}bulk_update_subscriptions 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.
Subscribe or unsubscribe multiple users to/from a subscription group. 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 bulk_update_subscriptions: 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.
bulk_update_subscriptions 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 bulk_update_subscriptions 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 bulk_update_subscriptions. 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.
bulk_update_subscriptions 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.