neuron_remove_bot_channel
Disconnect a WhatsApp channel from a bot. The bot will no longer respond to messages on this channel.
This record as markdown: /tools/io-github-conquext-neuron/neuron-remove-bot-channel.md
What neuron_remove_bot_channel does on Neuron
AI agents call neuron_remove_bot_channel 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 |
|---|---|---|---|
botId | string | Yes | Unique identifier (UUID) of the bot |
channelId | string | Yes | Unique identifier (UUID) of the WhatsApp channel to disconnect |
Parameters from the server's own tool schema.
Why neuron_remove_bot_channel is rated Critical
Disconnecting a channel from a bot is an irreversible operational action that removes an active communication link. While it may technically be re-attachable, the act of severing a live channel without an undo mechanism (no 'reconnect' implied) and the potential for dropped messages/disrupted service makes this Destructive.
From the tool's definition Disconnect a WhatsApp channel from a bot. The bot will no longer respond to messages on this channel.
Attacks that exploit this kind of access
The rule that runs neuron_remove_bot_channel 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_bot_channel, this is the rule to start with:
neuron_remove_bot_channel 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_bot_channel call is checked against it from then on.
Questions about neuron_remove_bot_channel
Disconnect a WhatsApp channel from a bot. The bot will no longer respond to messages on this channel. 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_bot_channel accepts 2 parameters: botId, channelId. Required: botId, 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_remove_bot_channel: 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_bot_channel 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_bot_channel 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_bot_channel. 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_bot_channel 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