get_campaigns
AI agents call get_campaigns 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.
The 'get_' prefix is a standard pattern for data retrieval without side effects. Mailchimp campaigns are business intelligence artifacts; retrieving them poses minimal risk. No modification, deletion, or execution occurs. Severity is low because campaign data is typically non-sensitive marketing metadata, and unauthorized read access, while undesirable, has limited blast radius compared to modification or deletion.
From the tool's definition Tool name 'get_campaigns' indicates retrieval of campaign data. Tool description is empty, but naming convention aligns with sibling Read tools (get_automation, get_automations, get_campaign) on this Mailchimp MCP server.
Attacks that exploit this kind of access
get_campaigns. 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_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 Mailchimp 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 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 →