create_connected_site
A write tool on the Mailchimp MCP server.
This record as markdown: /tools/damientilman-mailchimp-mcp-server/create-connected-site.md
What create_connected_site does on Mailchimp MCP
AI agents use create_connected_site to create or update resources in Mailchimp MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mailchimp MCP environment.
Why create_connected_site is rated Medium
An AI agent can call create_connected_site faster than any human can review: one bad instruction and it creates or modifies resources in Mailchimp MCP by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs create_connected_site 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 create_connected_site, this is the rule to start with:
create_connected_site stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 create_connected_site call is checked against it from then on.
Questions about create_connected_site
create_connected_site is a write tool on the Mailchimp MCP server. It is categorised as a Write tool in the Mailchimp MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mailchimp MCP server in PolicyLayer and add a rule for create_connected_site: 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.
create_connected_site is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_connected_site 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 create_connected_site. 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.
create_connected_site 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