mautic_contact_gdpr_erase
GDPR right-to-erasure: blank all personal data fields on a contact while keeping the contact record for audit trail. Uses overwriteWithBlank to actually clear field values. Blanks: firstname, lastname, email, phone, mobile, address1, address2, city, state, zipcode, country, company, position, tit...
This record as markdown: /tools/esanum-mcp-mautic/mautic-contact-gdpr-erase.md
What mautic_contact_gdpr_erase does on Mcp Mautic
AI agents call mautic_contact_gdpr_erase 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_contact_gdpr_erase is rated Critical
This tool irreversibly erases/blanks personal data fields. While the contact record is retained, the personal data values are permanently cleared and cannot be recovered.
From the tool's definition GDPR right-to-erasure: blank all personal data fields on a contact while keeping the contact record for audit trail. Uses overwriteWithBlank to actually clear field values.
Attacks that exploit this kind of access
The rule that runs mautic_contact_gdpr_erase 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_contact_gdpr_erase, this is the rule to start with:
mautic_contact_gdpr_erase 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_contact_gdpr_erase call is checked against it from then on.
Questions about mautic_contact_gdpr_erase
GDPR right-to-erasure: blank all personal data fields on a contact while keeping the contact record for audit trail. Uses overwriteWithBlank to actually clear field values. Blanks: firstname, lastname, email, phone, mobile, address1, address2, city, state, zipcode, country, company, position, title, fax, website, facebook, twitter, linkedin, instagram, skype. 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_contact_gdpr_erase: 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_contact_gdpr_erase 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_contact_gdpr_erase 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_contact_gdpr_erase. 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_contact_gdpr_erase 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