neuron_add_bot_channel
Connect an additional WhatsApp channel to a bot as a secondary number. The bot will respond to messages on this channel.
This record as markdown: /tools/io-github-conquext-neuron/neuron-add-bot-channel.md
What neuron_add_bot_channel does on Neuron
AI agents use neuron_add_bot_channel 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 |
|---|---|---|---|
botId | string | Yes | Unique identifier (UUID) of the bot |
channelId | string | Yes | Unique identifier (UUID) of the WhatsApp channel to connect |
Parameters from the server's own tool schema.
Why neuron_add_bot_channel is rated Medium
This is a Write operation: it creates a new association between a bot and a WhatsApp channel, modifying the bot's operational configuration reversibly. The severity is medium because misconfiguration could allow unauthorized channel access or unintended message routing, but the impact is limited to bot configuration rather than data deletion or financial consequences.
From the tool's definition The tool 'connects an additional WhatsApp channel to a bot' and enables the bot to 'respond to messages on this channel,' indicating it creates or modifies bot configuration to add a communication channel.
Attacks that exploit this kind of access
The rule that runs neuron_add_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_add_bot_channel, this is the rule to start with:
neuron_add_bot_channel 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_bot_channel call is checked against it from then on.
Questions about neuron_add_bot_channel
Connect an additional WhatsApp channel to a bot as a secondary number. The bot will respond to messages on this channel. 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_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_add_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_add_bot_channel 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_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_add_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_add_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.
This server
Across the catalogue