neuron_add_to_contact_list
Add one or more contacts to a list by contact ID or phone number. Phone numbers without existing contacts are auto-created as minimal contact records.
This record as markdown: /tools/io-github-conquext-neuron/neuron-add-to-contact-list.md
What neuron_add_to_contact_list does on Neuron
AI agents use neuron_add_to_contact_list 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 |
|---|---|---|---|
entries | array | Yes | Array of contacts to add, each identified by contactId or phone number |
idOrSlug | string | Yes | Unique identifier (UUID) or URL-friendly slug of the target contact list |
Parameters from the server's own tool schema.
Why neuron_add_to_contact_list is rated Medium
This tool creates new data (auto-creates minimal contact records) and modifies existing data (adds contacts to lists). These are reversible write operations. The severity is medium because while contact list manipulation could enable spam or unwanted messaging campaigns at scale, it does not directly move money, delete data irreversibly, or execute arbitrary code.
From the tool's definition Add one or more contacts to a list by contact ID or phone number. Phone numbers without existing contacts are auto-created as minimal contact records. The tool creates new contact records and modifies contact list membership.
Attacks that exploit this kind of access
The rule that runs neuron_add_to_contact_list 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_add_to_contact_list, this is the rule to start with:
neuron_add_to_contact_list 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_add_to_contact_list call is checked against it from then on.
Questions about neuron_add_to_contact_list
Add one or more contacts to a list by contact ID or phone number. Phone numbers without existing contacts are auto-created as minimal contact records. 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_add_to_contact_list accepts 2 parameters: entries, idOrSlug. Required: entries, idOrSlug. 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_add_to_contact_list: 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_add_to_contact_list 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_add_to_contact_list 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_add_to_contact_list. 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_add_to_contact_list 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