neuron_leave_group
Make the bot leave a WhatsApp group. This action is irreversible — the bot will need to be re-added by an admin.
This record as markdown: /tools/io-github-conquext-neuron/neuron-leave-group.md
What neuron_leave_group does on Neuron
AI agents call neuron_leave_group 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 |
|---|---|---|---|
groupJid | string | Yes | Group JID (ending in @g.us) |
channelId | string | Yes | WhatsApp channel identifier (UUID) |
Parameters from the server's own tool schema.
Why neuron_leave_group is rated Critical
The tool irreversibly removes the bot from a WhatsApp group and cannot be undone without manual intervention by an admin. This meets the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' The explicit note that the action is 'irreversible' confirms this classification.
From the tool's definition Make the bot leave a WhatsApp group. This action is irreversible — the bot will need to be re-added by an admin.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs neuron_leave_group 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_leave_group, this is the rule to start with:
neuron_leave_group 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_leave_group call is checked against it from then on.
Questions about neuron_leave_group
Make the bot leave a WhatsApp group. This action is irreversible — the bot will need to be re-added by an admin. 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_leave_group accepts 2 parameters: groupJid, channelId. Required: groupJid, channelId. 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_leave_group: 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_leave_group 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_leave_group 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_leave_group. 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_leave_group 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