mautic_get_contact_events
Get contact activity/timeline with event type filters. Use includeEvents to restrict to specific types: asset.download, campaign.event, campaign.event.scheduled, lead.donotcontact, email.failed, email.read, email.sent, email.click, form.submitted, lead.imported, page.hit, point.gained, stage.chan...
This record as markdown: /tools/esanum-mcp-mautic/mautic-get-contact-events.md
What mautic_get_contact_events does on Mcp Mautic
AI agents call mautic_get_contact_events to retrieve information from Mcp Mautic without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why mautic_get_contact_events is rated Low
This tool retrieves historical event/activity data for a contact with optional filtering by event type. It has no side effects, does not modify state, and only reads information from the marketing automation system. This is a classic Read operation with minimal risk if misused—an attacker might gain visibility into contact behavior patterns but cannot alter records or trigger actions.
From the tool's definition Tool description states 'Get contact activity/timeline with event type filters' - a retrieval operation with no modification capability. The includeEvents parameter only filters existing events; it does not create, modify, or delete any data.
Attacks that exploit this kind of access
The rule that runs mautic_get_contact_events 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_get_contact_events, this is the rule to start with:
mautic_get_contact_events is read-only, so it stays allowed. 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_get_contact_events call is checked against it from then on.
Questions about mautic_get_contact_events
Get contact activity/timeline with event type filters. Use includeEvents to restrict to specific types: asset.download, campaign.event, campaign.event.scheduled, lead.donotcontact, email.failed, email.read, email.sent, email.click, form.submitted, lead.imported, page.hit, point.gained, stage.changed, lead.utmtagsadded, page.videohit, lead.ipadded, lead.create, lead.identified, lead.merged. It is categorised as a Read tool in the Mcp Mautic MCP Server, which means it retrieves data without modifying state.
Register the Mcp Mautic MCP server in PolicyLayer and add a rule for mautic_get_contact_events: 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_get_contact_events is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the mautic_get_contact_events 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_get_contact_events. 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_get_contact_events 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