neuron_add_group_members
Add members to an existing group, resolved from any combination of sources (other groups, contact lists, contacts, pasted phones, all contacts). Address the group by its id, slug, or JID.
This record as markdown: /tools/io-github-conquext-neuron/neuron-add-group-members.md
What neuron_add_group_members does on Neuron
AI agents use neuron_add_group_members 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 |
|---|---|---|---|
tags | array | — | Keep only contacts carrying one of these tags |
group | string | Yes | Group id, slug, or JID (ending in @g.us) |
phones | array | — | Raw phone numbers, e.g. pasted from a CSV |
listIds | array | — | Contact list ids or slugs — pulls every member |
contactIds | array | — | Existing contact ids |
allContacts | boolean | — | Union the org's entire address book |
fromGroupIds | array | — | Copy/combine members live from these WhatsApp group JIDs |
excludeListIds | array | — | Subtract every member of these lists |
Parameters from the server's own tool schema.
Why neuron_add_group_members is rated Medium
An AI agent can call neuron_add_group_members faster than any human can review: one bad instruction and it creates or modifies resources in Neuron by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs neuron_add_group_members 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_group_members, this is the rule to start with:
neuron_add_group_members 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_group_members call is checked against it from then on.
Questions about neuron_add_group_members
Add members to an existing group, resolved from any combination of sources (other groups, contact lists, contacts, pasted phones, all contacts). Address the group by its id, slug, or JID. 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_group_members accepts 8 parameters: tags, group, phones, listIds, contactIds, allContacts, fromGroupIds, excludeListIds. Required: group. 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_group_members: 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_group_members 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_group_members 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_group_members. 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_group_members 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