Remove a newsletter subscriber by email address or unsubscribe token.
AI agents call newsletter_unsubscribe to permanently remove resources in Mcp Bot Crawler — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a subscriber from a newsletter list is a destructive action: the subscription record is deleted and the user is unsubscribed, which is not easily reversible without the user re-opting in. This could cause harm if misused at scale (e.g., bulk unsubscribing legitimate users). Severity is medium because it affects subscriber data but not financial records or core system integrity.
From the tool's definition 'Remove a newsletter subscriber by email address or unsubscribe token' — the word 'Remove' indicates an irreversible deletion of a subscriber record.
Attacks that exploit this kind of access
Remove a newsletter subscriber by email address or unsubscribe token. It is categorised as a Destructive tool in the Mcp Bot Crawler MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Bot Crawler MCP server in PolicyLayer and add a rule for newsletter_unsubscribe: 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 Mcp Bot Crawler. Nothing to install.
newsletter_unsubscribe is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the newsletter_unsubscribe 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 newsletter_unsubscribe. 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.
newsletter_unsubscribe is provided by the Mcp Bot Crawler MCP server (merulocal/hellogrowthcrmwebsite_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 →