mautic_get_campaign_event_log
Get the execution log for campaign events — shows which contacts triggered which campaign nodes and when. Queries the campaign_lead_event_log stats table. Filter by campaign_id, lead_id, event_id, or date range.
This record as markdown: /tools/esanum-mcp-mautic/mautic-get-campaign-event-log.md
What mautic_get_campaign_event_log does on Mcp Mautic
AI agents call mautic_get_campaign_event_log 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_campaign_event_log is rated Low
This tool retrieves historical log data about campaign event executions without modifying any data. It performs a simple query operation with filtering by standard criteria (campaign_id, lead_id, event_id, date range). This is a read-only operation with minimal risk if misused, as it only exposes existing log information.
From the tool's definition Tool description states 'Get the execution log' and 'Queries the campaign_lead_event_log stats table' with filtering capabilities. No modification, deletion, or execution of external operations is described.
Attacks that exploit this kind of access
The rule that runs mautic_get_campaign_event_log 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_campaign_event_log, this is the rule to start with:
mautic_get_campaign_event_log 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_campaign_event_log call is checked against it from then on.
Questions about mautic_get_campaign_event_log
Get the execution log for campaign events — shows which contacts triggered which campaign nodes and when. Queries the campaign_lead_event_log stats table. Filter by campaign_id, lead_id, event_id, or date range. 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_campaign_event_log: 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_campaign_event_log 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_campaign_event_log 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_campaign_event_log. 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_campaign_event_log 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