batch_replace_in_campaign_body
AI agents use batch_replace_in_campaign_body to create or update resources in Listmonk MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Listmonk MCP Server environment.
This tool performs a bulk find-and-replace operation on campaign content, which constitutes data modification (Write category). The 'batch' prefix suggests high-volume changes affecting multiple campaign instances or large portions of content, elevating severity to high due to potential for widespread unintended modifications.
From the tool's definition Tool name indicates 'batch_replace_in_campaign_body' which modifies campaign content in bulk. The parent server manages newsletters and campaigns, and a batch replacement operation in a campaign body would create or modify data at scale.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access batch_replace_in_campaign_body 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 batch_replace_in_campaign_body:
{
"version": "1",
"default": "deny",
"tools": {
"batch_replace_in_campaign_body": {
"limits": [
{
"counter": "batch_replace_in_campaign_body_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}batch_replace_in_campaign_body 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.
Free to start. No card required.
batch_replace_in_campaign_body. It is categorised as a Write tool in the Listmonk MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Listmonk MCP Server MCP server in PolicyLayer and add a rule for batch_replace_in_campaign_body: 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.
batch_replace_in_campaign_body 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 batch_replace_in_campaign_body 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 batch_replace_in_campaign_body. 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.
batch_replace_in_campaign_body 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.