Medium Risk

unsubscribe_user_by_userid

Unsubscribe a user from a subscription group by userId

How to control unsubscribe_user_by_userid ↓

What unsubscribe_user_by_userid does on Iterable MCP Server

AI agents use unsubscribe_user_by_userid 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.

Medium Risk

Why unsubscribe_user_by_userid needs a policy

This tool modifies a user's subscription status by removing them from a subscription group. It's a Write operation (modifying existing data/preferences) rather than Destructive because unsubscription is typically reversible (the user can be re-subscribed).

From the tool's definition Unsubscribe a user from a subscription group by userId

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

How to control unsubscribe_user_by_userid

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "unsubscribe_user_by_userid": {
      "limits": [
        {
          "counter": "unsubscribe_user_by_userid_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Iterable MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about unsubscribe_user_by_userid

What does the unsubscribe_user_by_userid tool do? +

Unsubscribe a user from a subscription group by userId. 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.

How do I enforce a policy on unsubscribe_user_by_userid? +

Register the Iterable MCP Server MCP server in PolicyLayer and add a rule for unsubscribe_user_by_userid: 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 unsubscribe_user_by_userid? +

unsubscribe_user_by_userid is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit unsubscribe_user_by_userid? +

Yes. Add a rate_limit block to the unsubscribe_user_by_userid 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 unsubscribe_user_by_userid completely? +

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

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

Free to start. No card required.

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.