neuron_merge_contact_lists
Merge two or more contact lists into a single unified list, deduplicating entries. Window merge creates a virtual union; materialized merge creates a static copy.
This record as markdown: /tools/io-github-conquext-neuron/neuron-merge-contact-lists.md
What neuron_merge_contact_lists does on Neuron
AI agents use neuron_merge_contact_lists 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 |
|---|---|---|---|
name | string | Yes | Display name for the resulting merged list |
slug | string | — | URL-friendly slug for the merged list (auto-generated if omitted) |
mergeType | string | Yes | Merge strategy: 'window' (virtual union, stays in sync) or 'materialized' (static copy at merge time) |
sourceListIds | array | Yes | UUIDs or slugs of the source lists to merge (minimum 2) |
Parameters from the server's own tool schema.
Why neuron_merge_contact_lists is rated Medium
The tool modifies data by combining contact lists and optionally persisting a new merged list. This is a reversible Write operation (the original lists typically remain and can be recreated or updated). It is not Destructive because the original contact lists are not deleted. It is not Execute because it doesn't run arbitrary code.
From the tool's definition Tool description states it 'Merge[s] two or more contact lists into a single unified list' and creates either 'a virtual union' or 'a static copy' — both are data modification operations.
Attacks that exploit this kind of access
The rule that runs neuron_merge_contact_lists 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_merge_contact_lists, this is the rule to start with:
neuron_merge_contact_lists 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_merge_contact_lists call is checked against it from then on.
Questions about neuron_merge_contact_lists
Merge two or more contact lists into a single unified list, deduplicating entries. Window merge creates a virtual union; materialized merge creates a static copy. 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_merge_contact_lists accepts 4 parameters: name, slug, mergeType, sourceListIds. Required: name, mergeType, sourceListIds. 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_merge_contact_lists: 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_merge_contact_lists 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_merge_contact_lists 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_merge_contact_lists. 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_merge_contact_lists 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