mautic_batch_delete_contacts
Delete multiple contacts in a single request
This record as markdown: /tools/esanum-mcp-mautic/mautic-batch-delete-contacts.md
What mautic_batch_delete_contacts does on Mcp Mautic
AI agents call mautic_batch_delete_contacts to permanently remove resources in Mcp Mautic, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why mautic_batch_delete_contacts is rated Critical
This tool permanently removes contact records from the Mautic system with no undo mechanism. Deletion is irreversible and affects business data at scale (batch operation). An AI agent with access could maliciously or accidentally wipe customer databases, making this a Destructive action with high blast radius despite not affecting financial transactions directly.
From the tool's definition Tool name explicitly states 'batch_delete_contacts' and description confirms 'Delete multiple contacts in a single request'
Attacks that exploit this kind of access
The rule that runs mautic_batch_delete_contacts 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_batch_delete_contacts, this is the rule to start with:
mautic_batch_delete_contacts is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Mautic, apply this rule, and every mautic_batch_delete_contacts call is checked against it from then on.
Questions about mautic_batch_delete_contacts
Delete multiple contacts in a single request. It is categorised as a Destructive tool in the Mcp Mautic MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Mautic MCP server in PolicyLayer and add a rule for mautic_batch_delete_contacts: 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_batch_delete_contacts is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the mautic_batch_delete_contacts 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_batch_delete_contacts. 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_batch_delete_contacts 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