list_merge_fields

A read tool on the Mailchimp MCP server.

SERVERMailchimp MCP SOURCEdamientilman/mailchimp-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/damientilman-mailchimp-mcp-server/list-merge-fields.md

WHAT IT DOES

What list_merge_fields does on Mailchimp MCP

AI agents call list_merge_fields 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.

RISK

Why list_merge_fields is rated Low

The tool appears to retrieve/query merge fields configuration from Mailchimp, which is a non-destructive read operation. No side effects or data modification are indicated by the name. Empty description lowers confidence slightly, but the naming pattern and context of sibling tools (which include write, execute, and create operations) reinforces this as a read-only retrieval function.

From the tool's definition Tool name 'list_merge_fields' indicates a query operation. The 'list_' prefix strongly suggests retrieval of merge field data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_merge_fields 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 list_merge_fields, this is the rule to start with:

list_merge_fields Allowed

list_merge_fields is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_merge_fields": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mailchimp MCP, apply this rule, and every list_merge_fields call is checked against it from then on.

FAQ

Questions about list_merge_fields

What does the list_merge_fields tool do? +

list_merge_fields 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.

How do I enforce a policy on list_merge_fields? +

Register the Mailchimp MCP server in PolicyLayer and add a rule for list_merge_fields: 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.

What risk level is list_merge_fields? +

list_merge_fields is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_merge_fields? +

Yes. Add a rate_limit block to the list_merge_fields 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.

How do I block list_merge_fields completely? +

Set action: deny in the PolicyLayer policy for list_merge_fields. 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.

What MCP server provides list_merge_fields? +

list_merge_fields 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.

KEEP EXPLORING

More on Mailchimp, and thousands of servers like it.

This server

All 227 Mailchimp tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →