neuron_send_whatsapp
Send a WhatsApp message to a phone number or group. Auto-resolves which channel to use (org default > first connected). Supports text, image, audio, video, and document types.
This record as markdown: /tools/io-github-conquext-neuron/neuron-send-whatsapp.md
What neuron_send_whatsapp does on Neuron
AI agents use neuron_send_whatsapp 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 |
|---|---|---|---|
to | string | Yes | Recipient: phone number (e.g., '2348012345678') or group JID (e.g., '120363XXX@g.us') |
text | string | Yes | Message text content |
sendAt | string | — | ISO 8601 date-time for scheduled delivery (e.g., '2025-12-31T10:00:00Z'). Message sends immediately if omitted. |
mediaUrl | string | — | URL of media to attach (required for non-text message types) |
channelId | string | — | Unique identifier (UUID) of a specific channel to override auto-resolution |
contactName | string | — | Display name for the recipient contact |
messageType | string | — | Message type: 'text' (default), 'image', 'audio', 'video', or 'document' |
Parameters from the server's own tool schema.
Why neuron_send_whatsapp is rated Medium
An AI agent can call neuron_send_whatsapp 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.
Attacks that exploit this kind of access
The rule that runs neuron_send_whatsapp 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_whatsapp, this is the rule to start with:
neuron_send_whatsapp 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_whatsapp call is checked against it from then on.
Questions about neuron_send_whatsapp
Send a WhatsApp message to a phone number or group. Auto-resolves which channel to use (org default > first connected). Supports text, image, audio, video, and document types. 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_whatsapp accepts 7 parameters: to, text, sendAt, mediaUrl, channelId, contactName, messageType. Required: to, text. 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_whatsapp: 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_whatsapp 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_whatsapp 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_whatsapp. 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_whatsapp 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