neuron_assign_bot_to_channel
Assign a bot to handle incoming messages on a specific WhatsApp channel. Replaces any previously assigned bot.
This record as markdown: /tools/io-github-conquext-neuron/neuron-assign-bot-to-channel.md
What neuron_assign_bot_to_channel does on Neuron
AI agents use neuron_assign_bot_to_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 |
|---|---|---|---|
id | string | Yes | Unique identifier (UUID) of the channel |
botId | string | Yes | Unique identifier (UUID) of the bot to assign |
Parameters from the server's own tool schema.
Why neuron_assign_bot_to_channel is rated Medium
This tool modifies configuration by assigning a bot to a channel and replaces previous assignments. This is a reversible write operation that changes the state of which bot handles messages on a channel. While it affects message routing, it does not delete data (Destructive), execute arbitrary code (Execute), or move money (Financial).
From the tool's definition Assign a bot to handle incoming messages on a specific WhatsApp channel. Replaces any previously assigned bot.
Attacks that exploit this kind of access
The rule that runs neuron_assign_bot_to_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_assign_bot_to_channel, this is the rule to start with:
neuron_assign_bot_to_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_assign_bot_to_channel call is checked against it from then on.
Questions about neuron_assign_bot_to_channel
Assign a bot to handle incoming messages on a specific WhatsApp channel. Replaces any previously assigned bot. 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_assign_bot_to_channel accepts 2 parameters: id, botId. Required: id, botId. 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_assign_bot_to_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_assign_bot_to_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_assign_bot_to_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_assign_bot_to_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_assign_bot_to_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