neuron_create_broadcast

Create a new broadcast message in draft status. Provide recipients directly or use recipientSources to resolve from contact lists. The WhatsApp channel is auto-resolved if not specified.

SERVERNeuron SOURCEneuron-mcp-server

Medium RISK CLASS

Category Write

Parameters 101 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-create-broadcast.md

WHAT IT DOES

What neuron_create_broadcast does on Neuron

AI agents use neuron_create_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
`name`	string	Yes	Display name or label for the broadcast
`botId`	string	—	Identifier (UUID) of a bot to send through. Each recipient's channel is picked by the bot's load-balancer + sticky sessions. Takes precedence over channelId.
`message`	string	—	Message content to broadcast to recipients (optional when sending a template)
`mediaUrl`	string	—	URL of media to attach (required for image or document message types)
`template`	object	—	Approved template (official WhatsApp Business API sessions only). On official API sessions, use one for broadcasts: most recipients won't have messaged you in t
`channelId`	string	—	Identifier (UUID) of the WhatsApp channel to send through (auto-resolved from default channel if omitted)
`recipients`	array	—	Direct list of recipients (alternative to recipientSources)
`messageType`	string	—	Type of message to send (e.g., 'text', 'image', 'document', or 'template' on official API sessions)
`scheduledAt`	string	—	ISO 8601 date-time for scheduled broadcast delivery (e.g., '2025-12-31T10:00:00Z'). Creates as draft if omitted.
`recipientSources`	object	—	Resolve recipients dynamically from contact lists with filtering and exclusion

Parameters from the server's own tool schema.

RISK

Why neuron_create_broadcast is rated Medium

An AI agent can call neuron_create_broadcast faster than any human can review: one bad instruction and it creates or modifies resources in Neuron by the hundred, each call as confident as the last.

Risk signalsAccepts raw HTML/template content (template) · High parameter count (20 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

neuron_create_broadcast Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "neuron_create_broadcast": {
      "limits": [
        {
          "counter": "neuron_create_broadcast_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_create_broadcast call is checked against it from then on.

FAQ

Questions about neuron_create_broadcast

What does the neuron_create_broadcast tool do? +

Create a new broadcast message in draft status. Provide recipients directly or use recipientSources to resolve from contact lists. The WhatsApp channel is auto-resolved if not specified. 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_create_broadcast accept? +

neuron_create_broadcast accepts 10 parameters: name, botId, message, mediaUrl, template, channelId, recipients, messageType, scheduledAt, recipientSources. Required: name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on neuron_create_broadcast? +

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

What risk level is neuron_create_broadcast? +

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

Can I rate-limit neuron_create_broadcast? +

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

How do I block neuron_create_broadcast completely? +

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

What MCP server provides neuron_create_broadcast? +

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

KEEP EXPLORING

More on Neuron, and thousands of servers like it.

This server

All 401 Neuron tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

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