neuron_import_contacts
Bulk import multiple contacts into the organization's address book. Accepts an array of contact objects with name, phone, and optional fields.
This record as markdown: /tools/io-github-conquext-neuron/neuron-import-contacts.md
What neuron_import_contacts does on Neuron
AI agents use neuron_import_contacts to create or update resources in Neuron, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Neuron environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
contacts | array | Yes | Array of contact objects to import into the organization |
Parameters from the server's own tool schema.
Why neuron_import_contacts is rated Medium
This tool creates or adds new contact records in bulk to the organization's address book. It is reversible (contacts can be deleted or updated later) and has no irreversible destructive effects.
From the tool's definition Tool description states 'Bulk import multiple contacts into the organization's address book' - the word 'import' indicates creation/addition of contact records.
Attacks that exploit this kind of access
The rule that runs neuron_import_contacts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Neuron, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For neuron_import_contacts, this is the rule to start with:
neuron_import_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 Neuron, apply this rule, and every neuron_import_contacts call is checked against it from then on.
Questions about neuron_import_contacts
Bulk import multiple contacts into the organization's address book. Accepts an array of contact objects with name, phone, and optional fields. It is categorised as a Write tool in the Neuron MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
neuron_import_contacts accepts 1 parameter: contacts. Required: contacts. The full parameter table on this page comes from the server's own tool schema.
Register the Neuron MCP server in PolicyLayer and add a rule for neuron_import_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 Neuron. Nothing to install.
neuron_import_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 neuron_import_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 neuron_import_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.
neuron_import_contacts is provided by the Neuron MCP server (neuron-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Neuron, and thousands of servers like it.
This server
Across the catalogue