neuron_post_to_newsletter
Post a message to a WhatsApp Channel newsletter. All subscribers receive the message. Provide at least one of text or mediaUrl. This triggers delivery and cannot be undone.
This record as markdown: /tools/io-github-conquext-neuron/neuron-post-to-newsletter.md
What neuron_post_to_newsletter does on Neuron
AI agents call neuron_post_to_newsletter 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 newsletter to post to |
text | string | — | Message text or caption to post to the newsletter |
mediaUrl | string | — | URL of the media file to attach (required for image, video, or document types) |
messageType | string | — | Type of message to send (default: 'text') |
Parameters from the server's own tool schema.
Why neuron_post_to_newsletter is rated Critical
While the primary effect is message delivery (which could seem like 'Write'), the specification that it 'cannot be undone' elevates this to Destructive category. Once posted to all newsletter subscribers, the message cannot be recalled or reversed. The blast radius is high: an AI agent with access could spam all subscribers, cause reputational damage, or send harmful content to a large audience irreversibly.
From the tool's definition Tool description explicitly states 'This triggers delivery and cannot be undone' — indicating an irreversible action. Posting to a newsletter that reaches 'all subscribers' constitutes a mass communication action with permanent consequences.
Attacks that exploit this kind of access
The rule that runs neuron_post_to_newsletter 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_newsletter, this is the rule to start with:
neuron_post_to_newsletter 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_newsletter call is checked against it from then on.
Questions about neuron_post_to_newsletter
Post a message to a WhatsApp Channel newsletter. All subscribers receive the message. Provide at least one of text or mediaUrl. 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_newsletter accepts 4 parameters: id, text, mediaUrl, messageType. 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_post_to_newsletter: 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_newsletter 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_newsletter 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_newsletter. 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_newsletter 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