mautic_get_bulk_activity
Get activity events across ALL contacts (not tied to a single contact). WARNING: This endpoint is very expensive on large instances — always use dateFrom/dateTo and includeEvents filters to avoid 504 timeouts. Prefer mautic_get_contact_events for single-contact timelines. Returns paginated results.
This record as markdown: /tools/esanum-mcp-mautic/mautic-get-bulk-activity.md
What mautic_get_bulk_activity does on Mcp Mautic
AI agents call mautic_get_bulk_activity 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_bulk_activity is rated Low
This is a read operation that retrieves activity data without creating, modifying, deleting, or executing operations. Severity is medium rather than low due to the warning about significant performance costs and potential 504 timeouts on large instances, which could impact system availability if misused by an agent without proper filtering—but the tool itself performs no destructive or side-effect operations.
From the tool's definition Tool name 'mautic_get_bulk_activity' and description 'Get activity events across ALL contacts' indicate data retrieval with no modification. Returns paginated results with optional filtering parameters (dateFrom/dateTo/includeEvents).
Attacks that exploit this kind of access
The rule that runs mautic_get_bulk_activity 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_bulk_activity, this is the rule to start with:
mautic_get_bulk_activity 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_bulk_activity call is checked against it from then on.
Questions about mautic_get_bulk_activity
Get activity events across ALL contacts (not tied to a single contact). WARNING: This endpoint is very expensive on large instances — always use dateFrom/dateTo and includeEvents filters to avoid 504 timeouts. Prefer mautic_get_contact_events for single-contact timelines. Returns paginated results. 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_bulk_activity: 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_bulk_activity 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_bulk_activity 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_bulk_activity. 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_bulk_activity 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