AI agents invoke send_campaign to trigger actions in Listmonk MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Sending a campaign dispatches emails to potentially thousands of subscribers immediately. While not strictly 'destructive' in the data-deletion sense, it is an irreversible external operation (emails cannot be unsent) with high blast radius if misused. Execute is the appropriate category as it triggers a significant external operation; severity is high due to potential for mass unsolicited email delivery.
From the tool's definition 'Send a campaign immediately' - triggers an external operation (mass email delivery) whose effects depend on arguments and cannot be trivially undone
Documented attack patterns abuse exactly the kind of access send_campaign 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 send_campaign:
{
"version": "1",
"default": "deny",
"tools": {
"send_campaign": {
"limits": [
{
"counter": "send_campaign_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}send_campaign stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Send a campaign immediately. It is categorised as a Execute tool in the Listmonk MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Listmonk MCP Server MCP server in PolicyLayer and add a rule for send_campaign: 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.
send_campaign is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the send_campaign 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 send_campaign. 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.
send_campaign 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.