neuron_send_broadcast
Send a broadcast message to all its recipients. The broadcast must be in draft status. This triggers message delivery and cannot be undone.
This record as markdown: /tools/io-github-conquext-neuron/neuron-send-broadcast.md
What neuron_send_broadcast does on Neuron
AI agents call neuron_send_broadcast to permanently remove resources in Neuron, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Unique identifier (UUID) of the broadcast to send |
Parameters from the server's own tool schema.
Why neuron_send_broadcast is rated Critical
While broadcast sending might appear to be an Execute action (triggering external operations), the explicit statement that it "cannot be undone" elevates this to Destructive category. Once sent to all recipients, the broadcast message delivery is irreversible, and any errors in targeting, content, or timing cannot be corrected.
From the tool's definition "Send a broadcast message to all its recipients" combined with "cannot be undone" indicates an irreversible action affecting potentially large populations.
Attacks that exploit this kind of access
The rule that runs neuron_send_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_send_broadcast, this is the rule to start with:
neuron_send_broadcast is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Neuron, apply this rule, and every neuron_send_broadcast call is checked against it from then on.
Questions about neuron_send_broadcast
Send a broadcast message to all its recipients. The broadcast must be in draft status. This triggers message delivery and cannot be undone. It is categorised as a Destructive tool in the Neuron MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
neuron_send_broadcast accepts 1 parameter: id. 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_send_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_send_broadcast is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the neuron_send_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_send_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_send_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.
Across the catalogue