mautic_create_form_action
Add a post-submission action to a form. Common types: lead.pointschange, form.repost, email.send.lead, lead.addtosegment. NOTE: Some Mautic versions may not support this standalone endpoint (404) — in that case, include actions in the form create/update payload instead.
This record as markdown: /tools/esanum-mcp-mautic/mautic-create-form-action.md
What mautic_create_form_action does on Mcp Mautic
AI agents use mautic_create_form_action 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_form_action is rated Medium
This tool creates or adds new actions to forms, which modifies form behavior and triggers automation workflows. While it doesn't delete data or execute arbitrary code, it does reversibly write/create configuration changes.
From the tool's definition Tool description states 'Add a post-submission action to a form' with action types like 'lead.pointschange', 'form.repost', 'email.send.lead', 'lead.addtosegment' — these are modifications to form configurations that create or add automation workflows.
Attacks that exploit this kind of access
The rule that runs mautic_create_form_action 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_form_action, this is the rule to start with:
mautic_create_form_action 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_form_action call is checked against it from then on.
Questions about mautic_create_form_action
Add a post-submission action to a form. Common types: lead.pointschange, form.repost, email.send.lead, lead.addtosegment. NOTE: Some Mautic versions may not support this standalone endpoint (404) — in that case, include actions in the form create/update payload instead. 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_form_action: 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_form_action 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_form_action 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_form_action. 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_form_action 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