neuron_update_broadcast
Update an existing broadcast's name, message content, or media before sending. The broadcast must still be in draft status.
This record as markdown: /tools/io-github-conquext-neuron/neuron-update-broadcast.md
What neuron_update_broadcast does on Neuron
AI agents use neuron_update_broadcast 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 broadcast to update |
name | string | — | New display name or label for the broadcast |
message | string | — | New message content to broadcast |
mediaUrl | string | — | New media URL to attach |
messageType | string | — | New message type (e.g., 'text', 'image', 'document') |
Parameters from the server's own tool schema.
Why neuron_update_broadcast is rated Medium
This tool creates or modifies data reversibly. It updates broadcast properties (name, content, media) before the broadcast is sent, which is a reversible write operation. The modification is non-destructive and does not execute actions, trigger financial transactions, or permanently delete data.
From the tool's definition Tool name contains 'update'; description states it modifies 'name, message content, or media' of an existing broadcast in draft status
Attacks that exploit this kind of access
The rule that runs neuron_update_broadcast 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_broadcast, this is the rule to start with:
neuron_update_broadcast 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_broadcast call is checked against it from then on.
Questions about neuron_update_broadcast
Update an existing broadcast's name, message content, or media before sending. The broadcast must still be in draft status. 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_broadcast accepts 5 parameters: id, name, message, mediaUrl, messageType. Required: id. 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_broadcast: 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_broadcast 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_broadcast 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_broadcast. 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_broadcast 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