mautic_update_contact
Update a Mautic contact with standard or custom field aliases. Set overwriteWithBlank=true to allow clearing fields by sending empty/null values (required for GDPR right-to-erasure). By default Mautic silently ignores empty values on PATCH.
This record as markdown: /tools/esanum-mcp-mautic/mautic-update-contact.md
What mautic_update_contact does on Mcp Mautic
AI agents use mautic_update_contact to create or update resources in Mcp Mautic, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Mautic environment.
Why mautic_update_contact is rated Medium
This tool creates or modifies contact data reversibly through PATCH operations. While it can clear fields (potentially sensitive for GDPR), the action is reversible—data can be re-added or restored from backups. It does not permanently delete records or execute arbitrary code.
From the tool's definition Tool name "mautic_update_contact" and description stating it can "Update a Mautic contact with standard or custom field aliases" and "clearing fields by sending empty/null values". The overwriteWithBlank parameter enables modification of existing contact data.
Attacks that exploit this kind of access
The rule that runs mautic_update_contact 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_update_contact, this is the rule to start with:
mautic_update_contact 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 Mcp Mautic, apply this rule, and every mautic_update_contact call is checked against it from then on.
Questions about mautic_update_contact
Update a Mautic contact with standard or custom field aliases. Set overwriteWithBlank=true to allow clearing fields by sending empty/null values (required for GDPR right-to-erasure). By default Mautic silently ignores empty values on PATCH. It is categorised as a Write tool in the Mcp Mautic MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Mautic MCP server in PolicyLayer and add a rule for mautic_update_contact: 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_update_contact 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 mautic_update_contact 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_update_contact. 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_update_contact 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.
This server
Across the catalogue