neuron_update_channel

Update configuration of an existing WhatsApp channel. Only provided fields are modified; omitted fields remain unchanged.

SERVERNeuron SOURCEneuron-mcp-server

Medium RISK CLASS

Category Write

Parameters 51 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-update-channel.md

WHAT IT DOES

What neuron_update_channel does on Neuron

AI agents use neuron_update_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 to update
`name`	string	—	New display name for the channel
`phoneNumber`	string	—	New phone number for the channel (E.164 format)
`metaAccessToken`	string	—	New Meta Access Token (meta_cloud channels only)
`metaPhoneNumberId`	string	—	New Meta Phone Number ID (meta_cloud channels only)

Parameters from the server's own tool schema.

RISK

Why neuron_update_channel is rated Medium

This tool modifies existing channel configuration data reversibly. It is a Write operation rather than Execute because it directly updates configuration settings rather than triggering external operations or code execution. It is not Destructive because changes are reversible (fields can be re-modified).

From the tool's definition Tool description explicitly states 'Update configuration of an existing WhatsApp channel' and 'Only provided fields are modified; omitted fields remain unchanged.' This is a modification operation on channel configuration.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs neuron_update_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_update_channel, this is the rule to start with:

neuron_update_channel Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "neuron_update_channel": {
      "limits": [
        {
          "counter": "neuron_update_channel_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Neuron, apply this rule, and every neuron_update_channel call is checked against it from then on.

FAQ

Questions about neuron_update_channel

What does the neuron_update_channel tool do? +

Update configuration of an existing WhatsApp channel. Only provided fields are modified; omitted fields remain unchanged. 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.

What parameters does neuron_update_channel accept? +

neuron_update_channel accepts 5 parameters: id, name, phoneNumber, metaAccessToken, metaPhoneNumberId. 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_update_channel? +

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

What risk level is neuron_update_channel? +

neuron_update_channel is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit neuron_update_channel? +

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

How do I block neuron_update_channel completely? +

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

What MCP server provides neuron_update_channel? +

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

KEEP EXPLORING

More on Neuron, and thousands of servers like it.

This server

All 231 Neuron tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →