mautic_import_contacts_csv
Import contacts from CSV text. Parses the CSV and batch-creates contacts via /api/contacts/batch/new in chunks. First row must be headers (field aliases). No CSV upload API exists in Mautic — this is the recommended workaround.
This record as markdown: /tools/esanum-mcp-mautic/mautic-import-contacts-csv.md
What mautic_import_contacts_csv does on Mcp Mautic
AI agents use mautic_import_contacts_csv to create or update resources in Mcp Mautic, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Mautic environment.
Why mautic_import_contacts_csv is rated Medium
This tool creates or modifies data (contacts) in bulk by parsing CSV and calling the batch creation endpoint. This is a Write operation—it generates new records that can be subsequently deleted or modified. While it affects multiple contacts at once (bulk operation), it does not delete, overwrite irreversibly, execute arbitrary code, or move money.
From the tool's definition Tool description states it 'batch-creates contacts' via the Mautic API. The action is reversible through normal contact deletion/management operations.
Attacks that exploit this kind of access
The rule that runs mautic_import_contacts_csv 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_import_contacts_csv, this is the rule to start with:
mautic_import_contacts_csv stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_import_contacts_csv call is checked against it from then on.
Questions about mautic_import_contacts_csv
Import contacts from CSV text. Parses the CSV and batch-creates contacts via /api/contacts/batch/new in chunks. First row must be headers (field aliases). No CSV upload API exists in Mautic — this is the recommended workaround. It is categorised as a Write tool in the Mcp Mautic MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Mautic MCP server in PolicyLayer and add a rule for mautic_import_contacts_csv: 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_import_contacts_csv is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the mautic_import_contacts_csv 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_import_contacts_csv. 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_import_contacts_csv 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