mautic_send_email_to_contact
Send email to contact. Supports custom tokens (dynamic placeholders like {custom_link}) and asset attachments. Tokens replace {token_name} in email body at send time.
This record as markdown: /tools/esanum-mcp-mautic/mautic-send-email-to-contact.md
What mautic_send_email_to_contact does on Mcp Mautic
AI agents invoke mautic_send_email_to_contact to trigger actions in Mcp Mautic. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why mautic_send_email_to_contact is rated High
Sending an email is an external operation with real-world side effects (email is delivered to a recipient). It is not merely writing data to a database; it triggers an irreversible external communication. This falls under Execute as it runs an external operation whose effects depend on arguments (recipient, content, tokens). Severity is high because a misused agent could spam or phish contacts at scale.
From the tool's definition 'Send email to contact' — triggers an external email delivery operation with custom tokens and asset attachments
Attacks that exploit this kind of access
The rule that runs mautic_send_email_to_contact 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_send_email_to_contact, this is the rule to start with:
mautic_send_email_to_contact stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_send_email_to_contact call is checked against it from then on.
Questions about mautic_send_email_to_contact
Send email to contact. Supports custom tokens (dynamic placeholders like {custom_link}) and asset attachments. Tokens replace {token_name} in email body at send time. It is categorised as a Execute tool in the Mcp Mautic MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Mautic MCP server in PolicyLayer and add a rule for mautic_send_email_to_contact: 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_send_email_to_contact is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the mautic_send_email_to_contact 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_send_email_to_contact. 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_send_email_to_contact 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