Get a specific campaign by ID including its full body content.
AI agents call get_campaign to retrieve information from Listmonk MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves campaign information from the Listmonk instance without modifying, deleting, or executing any operations. It is a simple query that returns existing data about a campaign based on its ID. There are no destructive, write, execute, or financial operations involved, making this a Read category tool with low severity.
From the tool's definition Tool name 'get_campaign' combined with description 'Get a specific campaign by ID including its full body content' indicates data retrieval with no side effects. The use of 'Get' verb and retrieval of campaign details are characteristic Read operations.
Documented attack patterns abuse exactly the kind of access get_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 get_campaign:
{
"version": "1",
"default": "deny",
"tools": {
"get_campaign": {}
}
}get_campaign is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get a specific campaign by ID including its full body content. It is categorised as a Read tool in the Listmonk MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Listmonk MCP Server MCP server in PolicyLayer and add a rule for get_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.
get_campaign is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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.