Add a subscriber to a list
AI agents use add_subscriber to create or update resources in Campaign Monitor MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Campaign Monitor MCP environment.
This tool creates new data (subscriber records) in a reversible manner—subscribers can be removed or modified later. It does not execute arbitrary code, delete data permanently, or move money. The severity is medium because misuse could lead to unauthorized subscriber additions, spam list inflation, or data integrity issues, but the action itself is not inherently destructive or financial.
From the tool's definition Tool name 'add_subscriber' and description 'Add a subscriber to a list' indicate creation of new subscriber records in a mailing list database.
Attacks that exploit this kind of access
Add a subscriber to a list. It is categorised as a Write tool in the Campaign Monitor MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Campaign Monitor MCP server in PolicyLayer and add a rule for add_subscriber: 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 Campaign Monitor MCP. Nothing to install.
add_subscriber 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 add_subscriber 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 add_subscriber. 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.
add_subscriber is provided by the Campaign Monitor MCP server (pauliowest/cmon-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →