neuron_post_to_status
Post a WhatsApp Status / Story from a connected direct (Baileys) WhatsApp number. Visible to the account's synced contacts for 24 hours — you do NOT specify recipients (the contact list is built automatically; pass statusJidList only to target a subset). Provide at least one of text or mediaUrl. ...
This record as markdown: /tools/io-github-conquext-neuron/neuron-post-to-status.md
What neuron_post_to_status does on Neuron
AI agents call neuron_post_to_status 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 |
|---|---|---|---|
font | integer | — | Text-status font index (0–9) |
text | string | — | Status text (for a text story) or caption (for media) |
mediaUrl | string | — | URL of the image/video/audio to post (required for non-text statuses) |
channelId | string | — | WhatsApp session channel UUID to post from. Omit to auto-resolve. |
messageType | string | — | Type of status (default: 'text') |
backgroundColor | string | — | Text-status background colour as hex, e.g. '#315575' |
Parameters from the server's own tool schema.
Why neuron_post_to_status is rated Critical
An AI agent that decides to call neuron_post_to_status doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Neuron is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs neuron_post_to_status 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_post_to_status, this is the rule to start with:
neuron_post_to_status 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_post_to_status call is checked against it from then on.
Questions about neuron_post_to_status
Post a WhatsApp Status / Story from a connected direct (Baileys) WhatsApp number. Visible to the account's synced contacts for 24 hours — you do NOT specify recipients (the contact list is built automatically; pass statusJidList only to target a subset). Provide at least one of text or mediaUrl. channelId is optional and auto-resolves to the default connected number. This triggers 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_post_to_status accepts 6 parameters: font, text, mediaUrl, channelId, messageType, backgroundColor. 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_post_to_status: 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_post_to_status 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_post_to_status 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_post_to_status. 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_post_to_status 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