get_campaign_click_details
AI agents call get_campaign_click_details to retrieve information from Mailchimp 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 click analytics for a campaign, which is a read-only operation that queries existing data without modification, deletion, or execution of external operations. The 'get_' prefix combined with 'click_details' indicates data retrieval. No side effects are implied.
From the tool's definition Tool name 'get_campaign_click_details' indicates retrieval of analytics/metrics data. Description is empty, but the naming pattern (get_* prefix) and context within a campaign management server strongly suggests a query operation returning campaign…
Attacks that exploit this kind of access
get_campaign_click_details. It is categorised as a Read tool in the Mailchimp MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Mailchimp MCP Server MCP server in PolicyLayer and add a rule for get_campaign_click_details: 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 Mailchimp MCP Server. Nothing to install.
get_campaign_click_details 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_click_details 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_click_details. 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_click_details is provided by the Mailchimp MCP Server MCP server (mattcoatsworth/mailchip-mcp-server). 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 →