neuron_update_group_subject
Update the name/subject of a WhatsApp group. Requires the bot to be a group admin.
This record as markdown: /tools/io-github-conquext-neuron/neuron-update-group-subject.md
What neuron_update_group_subject does on Neuron
AI agents use neuron_update_group_subject 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 |
|---|---|---|---|
subject | string | Yes | New group name/subject |
groupJid | string | Yes | Group JID (ending in @g.us) |
channelId | string | Yes | WhatsApp channel identifier (UUID) |
Parameters from the server's own tool schema.
Why neuron_update_group_subject is rated Medium
The tool modifies group properties (subject/name) reversibly. This is a Write operation rather than Read (it changes data) or Destructive (the change is reversible and the group continues to exist). Severity is medium because unauthorized group name changes could cause confusion or facilitate social engineering within group communications, but the impact is limited compared to data deletion or financial operations.
From the tool's definition Update the name/subject of a WhatsApp group. This is a modification operation that changes group metadata.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs neuron_update_group_subject 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_group_subject, this is the rule to start with:
neuron_update_group_subject 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_group_subject call is checked against it from then on.
Questions about neuron_update_group_subject
Update the name/subject of a WhatsApp group. Requires the bot to be a group admin. 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_group_subject accepts 3 parameters: subject, groupJid, channelId. Required: subject, groupJid, 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_group_subject: 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_group_subject 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_group_subject 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_group_subject. 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_group_subject 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