neuron_stop_channel_session

Stop the active Baileys session for the channel and disconnect from WhatsApp. The channel can be restarted later.

SERVERNeuron SOURCEneuron-mcp-server
High RISK CLASS
Category Execute
Parameters 11 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-conquext-neuron/neuron-stop-channel-session.md

What neuron_stop_channel_session does on Neuron

AI agents invoke neuron_stop_channel_session to trigger actions in Neuron. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

ParameterTypeRequiredDescription
id string Yes Unique identifier (UUID) of the Baileys channel to stop

Parameters from the server's own tool schema.

Why neuron_stop_channel_session is rated High

This tool executes a command to halt an active session and disconnect from WhatsApp. While the action is technically reversible (the channel 'can be restarted later'), the immediate effect is to interrupt service and connectivity. This fits the Execute category as it triggers an external operation whose effects depend on which channel is targeted.

From the tool's definition The tool description explicitly states 'Stop the active Baileys session for the channel and disconnect from WhatsApp.' This action triggers an external operation (disconnection from WhatsApp) that changes the operational state of a communication channel.

Questions about neuron_stop_channel_session

What does the neuron_stop_channel_session tool do? +

Stop the active Baileys session for the channel and disconnect from WhatsApp. The channel can be restarted later. It is categorised as a Execute tool in the Neuron MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does neuron_stop_channel_session accept? +

neuron_stop_channel_session accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on neuron_stop_channel_session? +

Register the Neuron MCP server in PolicyLayer and add a rule for neuron_stop_channel_session: 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.

What risk level is neuron_stop_channel_session? +

neuron_stop_channel_session is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit neuron_stop_channel_session? +

Yes. Add a rate_limit block to the neuron_stop_channel_session 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.

How do I block neuron_stop_channel_session completely? +

Set action: deny in the PolicyLayer policy for neuron_stop_channel_session. 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.

What MCP server provides neuron_stop_channel_session? +

neuron_stop_channel_session 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Neuron's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.