neuron_remove_group_members
Remove members from a group, resolved from any combination of sources — e.g. remove everyone on a contact list. Address the group by its id, slug, or JID.
This record as markdown: /tools/io-github-conquext-neuron/neuron-remove-group-members.md
What neuron_remove_group_members does on Neuron
AI agents call neuron_remove_group_members to permanently remove resources in Neuron, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| 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_remove_group_members is rated Critical
An AI agent that decides to call neuron_remove_group_members doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Neuron is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs neuron_remove_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_remove_group_members, this is the rule to start with:
neuron_remove_group_members is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Neuron, apply this rule, and every neuron_remove_group_members call is checked against it from then on.
Questions about neuron_remove_group_members
Remove members from a group, resolved from any combination of sources — e.g. remove everyone on a contact list. Address the group by its id, slug, or JID. It is categorised as a Destructive tool in the Neuron MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
neuron_remove_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_remove_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_remove_group_members is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the neuron_remove_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_remove_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_remove_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.
Across the catalogue