get_campaign_locations
A read tool on the Mailchimp MCP server.
This record as markdown: /tools/damientilman-mailchimp-mcp-server/get-campaign-locations.md
What get_campaign_locations does on Mailchimp MCP
AI agents call get_campaign_locations to retrieve information from Mailchimp MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_campaign_locations is rated Low
This tool retrieves campaign location information from Mailchimp. No side effects are indicated by the name or context. The 'get_' prefix is a strong signal of a Read operation. Even though the description is empty (reducing confidence slightly), the naming convention and context of a data query tool make it appropriate to classify as Read with low severity.
From the tool's definition Tool name 'get_campaign_locations' indicates a retrieval operation. Description is empty, but the semantic meaning of 'get_' prefix combined with sibling tools (add_member, create_campaign, batch_subscribe) that are clearly Write/Execute operations suggests…
Attacks that exploit this kind of access
The rule that runs get_campaign_locations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mailchimp MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_campaign_locations, this is the rule to start with:
get_campaign_locations is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mailchimp MCP, apply this rule, and every get_campaign_locations call is checked against it from then on.
Questions about get_campaign_locations
get_campaign_locations is a read tool on the Mailchimp MCP server. It is categorised as a Read tool in the Mailchimp MCP MCP Server, which means it retrieves data without modifying state.
Register the Mailchimp MCP server in PolicyLayer and add a rule for get_campaign_locations: 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. Nothing to install.
get_campaign_locations 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_locations 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_locations. 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_locations is provided by the Mailchimp MCP server (damientilman/mailchimp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mailchimp, and thousands of servers like it.
This server
Across the catalogue