mautic_delete_contact_field
Delete a custom contact field. WARNING: This permanently removes the field and all stored data for it across all contacts.
This record as markdown: /tools/esanum-mcp-mautic/mautic-delete-contact-field.md
What mautic_delete_contact_field does on Mcp Mautic
AI agents call mautic_delete_contact_field 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_delete_contact_field is rated Critical
This tool irreversibly deletes data (custom contact fields and all associated stored data across all contacts). Destructive operations that cannot be undone are classified as Destructive severity. The blast radius is high because it affects all contacts in the system, making this a high-severity destructive action that could cause significant business impact if invoked incorrectly by an AI agent.
From the tool's definition Tool description explicitly states 'Delete a custom contact field' and 'WARNING: This permanently removes the field and all stored data for it across all contacts.' The words 'permanently removes' and 'all stored data' indicate irreversible deletion.
Attacks that exploit this kind of access
The rule that runs mautic_delete_contact_field 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_delete_contact_field, this is the rule to start with:
mautic_delete_contact_field 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_delete_contact_field call is checked against it from then on.
Questions about mautic_delete_contact_field
Delete a custom contact field. WARNING: This permanently removes the field and all stored data for it across all contacts. 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_delete_contact_field: 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_delete_contact_field 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_delete_contact_field 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_delete_contact_field. 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_delete_contact_field 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