AI agents call remove_subscriber to permanently remove resources in Listmonk MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a subscriber from a mailing list is a destructive operation that cannot be undone without manual restoration. While not as critical as deleting entire lists or media files, it permanently removes subscriber data from the system. This is categorized as Destructive rather than Write because the operation is irreversible and eliminates data rather than modifying it reversibly.
From the tool's definition Tool name is 'remove_subscriber' and description states 'Remove a subscriber from Listmonk.' The verb 'remove' combined with the action of eliminating a subscriber record indicates irreversible deletion of data.
Documented attack patterns abuse exactly the kind of access remove_subscriber gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Listmonk MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_subscriber:
{
"version": "1",
"default": "deny",
"hide": [
"remove_subscriber"
]
}remove_subscriber disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove a subscriber from Listmonk. It is categorised as a Destructive tool in the Listmonk MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Listmonk MCP Server MCP server in PolicyLayer and add a rule for remove_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 Listmonk MCP Server. Nothing to install.
remove_subscriber 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 remove_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 remove_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.
remove_subscriber is provided by the Listmonk MCP Server MCP server (rhnvrm/listmonk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 Listmonk MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
29 Listmonk MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.