neuron_send_campaign_message
Send a campaign message to selected eligible contacts via WhatsApp. Requires the campaign to be in 'active' status and contacts to be eligible.
This record as markdown: /tools/io-github-conquext-neuron/neuron-send-campaign-message.md
What neuron_send_campaign_message does on Neuron
AI agents use neuron_send_campaign_message 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 active campaign |
contactIds | array | Yes | Array of contact UUIDs to send the campaign message to |
Parameters from the server's own tool schema.
Why neuron_send_campaign_message is rated Medium
This tool creates and sends messages to real WhatsApp users, which is a write operation that modifies state (message delivery logs, contact interaction history). While reversible in principle, the impact is high because mass messaging can violate spam regulations, damage reputation, incur costs, and affect user relationships.
From the tool's definition Tool name contains 'send' and description states 'Send a campaign message to selected eligible contacts via WhatsApp', indicating creation/transmission of outbound messages with side effects (delivery to external users).
Attacks that exploit this kind of access
The rule that runs neuron_send_campaign_message 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_campaign_message, this is the rule to start with:
neuron_send_campaign_message 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_send_campaign_message call is checked against it from then on.
Questions about neuron_send_campaign_message
Send a campaign message to selected eligible contacts via WhatsApp. Requires the campaign to be in 'active' status and contacts to be eligible. 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_send_campaign_message accepts 2 parameters: id, contactIds. Required: id, contactIds. 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_campaign_message: 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_campaign_message 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_send_campaign_message 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_campaign_message. 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_campaign_message 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