mautic_create_contact_field
Create a new custom contact field. Set isUniqueIdentifier to true to auto-merge contacts sharing the same value.
This record as markdown: /tools/esanum-mcp-mautic/mautic-create-contact-field.md
What mautic_create_contact_field does on Mcp Mautic
AI agents use mautic_create_contact_field 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_create_contact_field is rated Medium
This tool creates/adds schema elements (custom fields) rather than deleting them, making it Write rather than Destructive. While it can trigger contact merging via isUniqueIdentifier, this is configuration-driven and reversible. The blast radius is medium: misconfiguration could corrupt data organization or cause unwanted contact merges, but the operation itself doesn't permanently destroy data.
From the tool's definition Tool creates a new custom contact field, modifying the data schema. Description explicitly states 'Create a new custom contact field' indicating a data creation operation.
Attacks that exploit this kind of access
The rule that runs mautic_create_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_create_contact_field, this is the rule to start with:
mautic_create_contact_field 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_create_contact_field call is checked against it from then on.
Questions about mautic_create_contact_field
Create a new custom contact field. Set isUniqueIdentifier to true to auto-merge contacts sharing the same value. 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_create_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_create_contact_field 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_create_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_create_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_create_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.
This server
Across the catalogue