AI agents call get_campaigns 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 queries and retrieves campaign data without creating, modifying, or deleting any resources. It is a straightforward data retrieval operation that fits the Read category. The optional status filter is a read parameter for filtering results, not an action that modifies state. Severity is low because retrieving campaign metadata poses minimal risk even if accessed by an unauthorized agent.
From the tool's definition Tool name is 'get_campaigns' and description states 'Get all campaigns with optional status filter' - a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_campaigns 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_campaigns:
{
"version": "1",
"default": "deny",
"tools": {
"get_campaigns": {}
}
}get_campaigns 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 all campaigns with optional status filter. 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_campaigns: 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_campaigns 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_campaigns 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_campaigns. 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_campaigns 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.