neuron_set_presence
Set typing indicator or online/offline presence on a WhatsApp chat. Only supported on Baileys channels.
This record as markdown: /tools/io-github-conquext-neuron/neuron-set-presence.md
What neuron_set_presence does on Neuron
AI agents invoke neuron_set_presence to trigger actions in Neuron. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | string | Yes | Chat JID to set presence for |
type | string | Yes | Presence type |
channelId | string | Yes | WhatsApp channel identifier (UUID) |
Parameters from the server's own tool schema.
Why neuron_set_presence is rated High
This tool sends a real-time signal to WhatsApp (typing indicator or presence status), which is an external operation with side effects on a live messaging platform. It doesn't read, write persistent data, or delete anything, but it does trigger an observable external action. Severity is low because the blast radius is minimal — misuse would at worst cause spurious typing indicators or incorrect online/offline status.
From the tool's definition 'Set typing indicator or online/offline presence on a WhatsApp chat' — triggers an external operation (presence signal) on a live WhatsApp channel
Attacks that exploit this kind of access
The rule that runs neuron_set_presence 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_set_presence, this is the rule to start with:
neuron_set_presence stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_set_presence call is checked against it from then on.
Questions about neuron_set_presence
Set typing indicator or online/offline presence on a WhatsApp chat. Only supported on Baileys channels. It is categorised as a Execute tool in the Neuron MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
neuron_set_presence accepts 3 parameters: to, type, channelId. Required: to, type, channelId. 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_set_presence: 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_set_presence is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the neuron_set_presence 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_set_presence. 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_set_presence 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