Get which lists and segments a campaign was sent to
AI agents call get_campaign_lists_and_segments 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 campaign delivery information (which lists/segments received a campaign). It performs a query operation with no capacity to modify, delete, or execute external actions. The blast radius of misuse is minimal — an attacker gains visibility into past campaign targeting but cannot alter campaigns, subscribers, or account settings.
From the tool's definition Tool name is 'get_campaign_lists_and_segments' and description states 'Get which lists and segments a campaign was sent to' — both clearly indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get which lists and segments a campaign was sent to. 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_lists_and_segments: 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_lists_and_segments 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_lists_and_segments 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_lists_and_segments. 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_lists_and_segments 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 →