get_store_customer
A read tool on the Mailchimp MCP server.
This record as markdown: /tools/damientilman-mailchimp-mcp-server/get-store-customer.md
What get_store_customer does on Mailchimp MCP
AI agents call get_store_customer 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_store_customer is rated Low
The naming convention 'get_' strongly indicates a read operation that queries or retrieves customer data. There is no evidence of modification, deletion, or execution capabilities. While the empty description reduces confidence slightly, the name and context of sibling tools support classification as a Read operation with low severity risk.
From the tool's definition Tool name 'get_store_customer' follows a GET/retrieval pattern typical of read operations. The tool appears designed to retrieve customer data from a Mailchimp store integration.
Attacks that exploit this kind of access
The rule that runs get_store_customer 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_store_customer, this is the rule to start with:
get_store_customer 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_store_customer call is checked against it from then on.
Questions about get_store_customer
get_store_customer 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_store_customer: 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_store_customer 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_store_customer 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_store_customer. 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_store_customer 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