crm_bulk_create_contacts
Bulk-create contacts with dedupe + compliance checks: rows whose email or phone already match a do_not_contact contact are skipped, as are rows that would duplicate an existing contact.
This record as markdown: /tools/com-getmunin-munin/crm-bulk-create-contacts.md
What crm_bulk_create_contacts does on Munin
AI agents use crm_bulk_create_contacts to create or update resources in Munin, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Munin environment.
Why crm_bulk_create_contacts is rated Medium
This tool creates multiple contact records in a CRM system, which is a reversible write operation. While it includes safeguards (dedupe and compliance checks), bulk creation of contacts could enable spam, unauthorized contact lists, or data pollution if misused by an agent.
From the tool's definition Tool name contains 'bulk_create_contacts' and description states it creates contacts with deduplication checks. The verb 'create' indicates data modification.
Attacks that exploit this kind of access
The rule that runs crm_bulk_create_contacts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Munin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crm_bulk_create_contacts, this is the rule to start with:
crm_bulk_create_contacts 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 Munin, apply this rule, and every crm_bulk_create_contacts call is checked against it from then on.
Questions about crm_bulk_create_contacts
Bulk-create contacts with dedupe + compliance checks: rows whose email or phone already match a do_not_contact contact are skipped, as are rows that would duplicate an existing contact. It is categorised as a Write tool in the Munin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Munin MCP server in PolicyLayer and add a rule for crm_bulk_create_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 Munin. Nothing to install.
crm_bulk_create_contacts 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 crm_bulk_create_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 crm_bulk_create_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.
crm_bulk_create_contacts is provided by the Munin MCP server (https://mcp.getmunin.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Munin, and thousands of servers like it.
This server
Across the catalogue