neuron_update_profile_name
Update the bot's WhatsApp display name on the given channel.
This record as markdown: /tools/io-github-conquext-neuron/neuron-update-profile-name.md
What neuron_update_profile_name does on Neuron
AI agents use neuron_update_profile_name 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 |
|---|---|---|---|
name | string | Yes | New display name |
channelId | string | Yes | WhatsApp channel identifier (UUID) |
Parameters from the server's own tool schema.
Why neuron_update_profile_name is rated Medium
The tool modifies bot profile metadata (WhatsApp display name) but does not delete, execute code, move money, or perform irreversible actions. This is a straightforward data update operation. Severity is medium because unauthorized display name changes could enable impersonation or reputation damage in a WhatsApp communications context, but the change itself is fully reversible.
From the tool's definition Tool name includes 'update' and description states 'Update the bot's WhatsApp display name', indicating a reversible modification operation.
Attacks that exploit this kind of access
The rule that runs neuron_update_profile_name 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_profile_name, this is the rule to start with:
neuron_update_profile_name 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_update_profile_name call is checked against it from then on.
Questions about neuron_update_profile_name
Update the bot's WhatsApp display name on the given 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_update_profile_name accepts 2 parameters: name, channelId. Required: name, 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_update_profile_name: 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_update_profile_name 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_update_profile_name 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_update_profile_name. 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_update_profile_name 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