mautic_merge_contacts
Merge two contacts into one. Fetches both contacts, merges their data (target wins on conflicts, fills empty target fields from source), updates the target, and deletes the source. Note: this is a composite operation — Mautic v7 has no native merge API endpoint.
This record as markdown: /tools/esanum-mcp-mautic/mautic-merge-contacts.md
What mautic_merge_contacts does on Mcp Mautic
AI agents call mautic_merge_contacts to permanently remove resources in Mcp Mautic, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why mautic_merge_contacts is rated Critical
The tool irreversibly deletes the source contact after merging, which cannot be undone. This is a destructive operation with high blast radius as it permanently removes a contact record and overwrites target contact data.
From the tool's definition merges their data...updates the target, and deletes the source
Attacks that exploit this kind of access
The rule that runs mautic_merge_contacts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Mautic, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mautic_merge_contacts, this is the rule to start with:
mautic_merge_contacts is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Mautic, apply this rule, and every mautic_merge_contacts call is checked against it from then on.
Questions about mautic_merge_contacts
Merge two contacts into one. Fetches both contacts, merges their data (target wins on conflicts, fills empty target fields from source), updates the target, and deletes the source. Note: this is a composite operation — Mautic v7 has no native merge API endpoint. It is categorised as a Destructive tool in the Mcp Mautic MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Mautic MCP server in PolicyLayer and add a rule for mautic_merge_contacts: 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 Mcp Mautic. Nothing to install.
mautic_merge_contacts is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the mautic_merge_contacts 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 mautic_merge_contacts. 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.
mautic_merge_contacts is provided by the Mcp Mautic MCP server (esanum/mcp-mautic). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Mautic, and thousands of servers like it.
Across the catalogue