neuron_mark_as_read
Mark a WhatsApp message as read, sending read receipts to the sender.
This record as markdown: /tools/io-github-conquext-neuron/neuron-mark-as-read.md
What neuron_mark_as_read does on Neuron
AI agents use neuron_mark_as_read 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 |
|---|---|---|---|
chatJid | string | Yes | Chat JID the message belongs to |
channelId | string | Yes | WhatsApp channel identifier (UUID) |
messageId | string | Yes | WhatsApp message ID to mark as read |
Parameters from the server's own tool schema.
Why neuron_mark_as_read is rated Medium
This tool modifies message state by marking messages as read and sends read receipts, which is a reversible write operation. It does not execute arbitrary code, delete data, cause financial impact, or retrieve/query data alone. The severity is low because marking messages as read has minimal side effects and does not affect core data integrity or user security.
From the tool's definition Tool description states 'Mark a WhatsApp message as read, sending read receipts to the sender.' The verb 'mark' indicates a state change operation that modifies message metadata (read status) and sends read receipts.
Attacks that exploit this kind of access
The rule that runs neuron_mark_as_read 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_mark_as_read, this is the rule to start with:
neuron_mark_as_read 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_mark_as_read call is checked against it from then on.
Questions about neuron_mark_as_read
Mark a WhatsApp message as read, sending read receipts to the sender. 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_mark_as_read accepts 3 parameters: chatJid, channelId, messageId. Required: chatJid, channelId, messageId. 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_mark_as_read: 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_mark_as_read 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_mark_as_read 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_mark_as_read. 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_mark_as_read 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