mautic_remove_contact_utm
Remove a specific set of UTM tags from a contact
This record as markdown: /tools/esanum-mcp-mautic/mautic-remove-contact-utm.md
What mautic_remove_contact_utm does on Mcp Mautic
AI agents call mautic_remove_contact_utm 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_remove_contact_utm is rated Critical
Removing UTM tags from a contact deletes marketing attribution data that tracks how the contact was acquired. This action is likely irreversible (no indication of an undo or restore mechanism), making it Destructive. The blast radius is medium — it affects marketing attribution data for individual contacts but does not delete the contact itself or cause financial harm.
From the tool's definition 'Remove a specific set of UTM tags from a contact' — removal of UTM tag data is an irreversible deletion of attribution/tracking data associated with a contact
Attacks that exploit this kind of access
The rule that runs mautic_remove_contact_utm 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_remove_contact_utm, this is the rule to start with:
mautic_remove_contact_utm 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_remove_contact_utm call is checked against it from then on.
Questions about mautic_remove_contact_utm
Remove a specific set of UTM tags from a contact. 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_remove_contact_utm: 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_remove_contact_utm 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_remove_contact_utm 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_remove_contact_utm. 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_remove_contact_utm 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