neuron_remove_from_contact_list
Remove one or more contacts from a list by their contact IDs. Does not delete the contacts themselves.
This record as markdown: /tools/io-github-conquext-neuron/neuron-remove-from-contact-list.md
What neuron_remove_from_contact_list does on Neuron
AI agents use neuron_remove_from_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 |
|---|---|---|---|
idOrSlug | string | Yes | Unique identifier (UUID) or URL-friendly slug of the contact list |
contactIds | array | Yes | Array of contact UUIDs to remove from the list |
Parameters from the server's own tool schema.
Why neuron_remove_from_contact_list is rated Medium
The tool removes contacts from a list (a reversible modification of list membership) but explicitly does not delete the contacts themselves. This is a Write operation — it modifies a data association without permanent destruction of the underlying records.
From the tool's definition Remove one or more contacts from a list by their contact IDs. Does not delete the contacts themselves.
Attacks that exploit this kind of access
The rule that runs neuron_remove_from_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_remove_from_contact_list, this is the rule to start with:
neuron_remove_from_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_remove_from_contact_list call is checked against it from then on.
Questions about neuron_remove_from_contact_list
Remove one or more contacts from a list by their contact IDs. Does not delete the contacts themselves. 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_remove_from_contact_list accepts 2 parameters: idOrSlug, contactIds. Required: idOrSlug, contactIds. 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_remove_from_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_remove_from_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_remove_from_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_remove_from_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_remove_from_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