# mautic_delete_contact_field Delete a custom contact field. WARNING: This permanently removes the field and all stored data for it across all contacts. Agent View of the PolicyLayer registry record for `mautic_delete_contact_field`. HTML page: https://policylayer.com/tools/esanum-mcp-mautic/mautic-delete-contact-field ## Facts - Tool: `mautic_delete_contact_field` - Server: Mcp Mautic (`esanum/mcp-mautic`) — https://policylayer.com/tools/esanum-mcp-mautic.md - Homepage: https://github.com/esanum/mcp-mautic - Risk category: Destructive (Critical risk) - Registry record: grade F, identity unverified - Server rate-limited: no - Parameters: 0 - Recommended policy verdict: Hidden ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "mautic_delete_contact_field", "arguments": {} } } ``` ## 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 own 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." ## Use case 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. ## Recommended policy (PolicyLayer) Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp Mautic: ```json { "version": "1", "default": "deny", "hide": [ "mautic_delete_contact_field" ] } ``` ## Other tools on Mcp Mautic (228) - `mautic_batch_delete_contacts` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-batch-delete-contacts.md - `mautic_campaign_force_reentry` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-campaign-force-reentry.md - `mautic_contact_gdpr_erase` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-contact-gdpr-erase.md - `mautic_delete_asset` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-delete-asset.md - `mautic_delete_campaign` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-delete-campaign.md - `mautic_delete_category` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-delete-category.md - `mautic_delete_company` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-delete-company.md - `mautic_delete_company_field` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-delete-company-field.md - `mautic_delete_contact` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-delete-contact.md - `mautic_delete_dynamic_content` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-delete-dynamic-content.md - `mautic_delete_email` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-delete-email.md - `mautic_delete_file` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-delete-file.md - `mautic_delete_focus` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-delete-focus.md - `mautic_delete_form` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-delete-form.md - `mautic_delete_form_action` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-delete-form-action.md - `mautic_delete_form_field` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-delete-form-field.md - `mautic_delete_message` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-delete-message.md - `mautic_delete_note` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-delete-note.md - `mautic_delete_notification` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-delete-notification.md - `mautic_delete_page` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-delete-page.md - `mautic_delete_point_action` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-delete-point-action.md - `mautic_delete_point_group` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-delete-point-group.md - `mautic_delete_point_trigger` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-delete-point-trigger.md - `mautic_delete_role` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-delete-role.md - `mautic_delete_segment` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-delete-segment.md - `mautic_delete_sms` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-delete-sms.md - `mautic_delete_stage` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-delete-stage.md - `mautic_delete_tag` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-delete-tag.md - `mautic_delete_user` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-delete-user.md - `mautic_delete_webhook` — Destructive — https://policylayer.com/tools/esanum-mcp-mautic/mautic-delete-webhook.md - …and 198 more: https://policylayer.com/tools/esanum-mcp-mautic.md ## For agents This record is a snapshot. Live verdicts and the full registry: - Check every server in your MCP config at once: `npx -y policylayer stack` - Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md) - Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events` --- Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=esanum-mcp-mautic · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/esanum-mcp-mautic