neuron_edit_message
Edit the content of a previously sent message in a conversation. Only the message sender can edit their messages.
This record as markdown: /tools/io-github-conquext-neuron/neuron-edit-message.md
What neuron_edit_message does on Neuron
AI agents use neuron_edit_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 conversation |
msgId | string | Yes | Unique identifier (UUID) of the message to edit |
content | string | Yes | New text content to replace the existing message |
Parameters from the server's own tool schema.
Why neuron_edit_message is rated Medium
The tool modifies message content, which is a write operation. Severity is medium because an AI agent could misuse this to alter conversation history or spread misinformation by editing previously sent messages, but the effect is limited to messages the bot itself sent and is theoretically reversible (the original content is lost from the message itself, but this is not a destructive delete).
From the tool's definition Tool description states 'Edit the content of a previously sent message' — this is a reversible modification operation that alters existing data.
Risk signalsAccepts raw HTML/template content (content)
Attacks that exploit this kind of access
The rule that runs neuron_edit_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_edit_message, this is the rule to start with:
neuron_edit_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_edit_message call is checked against it from then on.
Questions about neuron_edit_message
Edit the content of a previously sent message in a conversation. Only the message sender can edit their messages. 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_edit_message accepts 3 parameters: id, msgId, content. Required: id, msgId, content. 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_edit_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_edit_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_edit_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_edit_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_edit_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