Get email client usage stats for a campaign
AI agents call get_campaign_email_client_usage 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 queries campaign analytics/statistics (email client usage data) with no side effects, reversible operations, code execution, data deletion, or financial impact. It is a read-only retrieval operation typical of analytics endpoints. The low severity reflects that misuse would only expose campaign analytics data, not enable destructive or unauthorized actions.
From the tool's definition Tool name contains 'get' and description states 'Get email client usage stats for a campaign' — this retrieves statistics about how a campaign performed across email clients without modifying any data.
Attacks that exploit this kind of access
Get email client usage stats 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_email_client_usage: 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_email_client_usage 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_email_client_usage 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_email_client_usage. 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_email_client_usage 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 →