neuron_update_newsletter
Update the name or description of an existing WhatsApp Channel newsletter. Only provided fields are changed.
This record as markdown: /tools/io-github-conquext-neuron/neuron-update-newsletter.md
What neuron_update_newsletter does on Neuron
AI agents use neuron_update_newsletter 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 newsletter to update |
name | string | — | New display name for the newsletter |
description | string | — | New description for the newsletter |
Parameters from the server's own tool schema.
Why neuron_update_newsletter is rated Medium
The tool modifies existing newsletter metadata (name and description) in a WhatsApp Channel system. This is a Write operation because it creates or modifies data reversibly—the changes can be undone by updating the fields again.
From the tool's definition Tool name contains 'update' and description states 'Update the name or description of an existing WhatsApp Channel newsletter. Only provided fields are changed.' This is a reversible modification of data.
Attacks that exploit this kind of access
The rule that runs neuron_update_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_update_newsletter, this is the rule to start with:
neuron_update_newsletter 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_update_newsletter call is checked against it from then on.
Questions about neuron_update_newsletter
Update the name or description of an existing WhatsApp Channel newsletter. Only provided fields are changed. 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_update_newsletter accepts 3 parameters: id, name, description. 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_update_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_update_newsletter 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_update_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_update_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_update_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.
This server
Across the catalogue