Get spam complaints for a campaign
AI agents call get_campaign_spam to retrieve information from Campaign Monitor MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical spam complaint data associated with a campaign. It performs a query operation with no side effects—it does not modify, delete, or execute actions on the data. The blast radius of misuse is minimal; an attacker could only gain visibility into spam metrics, which is sensitive but not actionable for account compromise or financial harm.
From the tool's definition Tool name 'get_campaign_spam' and description 'Get spam complaints for a campaign' indicate data retrieval with no modification or deletion of records.
Attacks that exploit this kind of access
Get spam complaints for a campaign. It is categorised as a Read tool in the Campaign Monitor MCP MCP Server, which means it retrieves data without modifying state.
Register the Campaign Monitor MCP server in PolicyLayer and add a rule for get_campaign_spam: 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 Campaign Monitor MCP. Nothing to install.
get_campaign_spam 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_spam 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_spam. 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_spam is provided by the Campaign Monitor MCP server (pauliowest/cmon-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →