neuron_update_scheduled_message

Update the message content, media, or send time of a scheduled message. Only messages with status 'scheduled' can be updated.

SERVERNeuron SOURCEneuron-mcp-server

Medium RISK CLASS

Category Write

Parameters 61 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-conquext-neuron/neuron-update-scheduled-message.md

WHAT IT DOES

What neuron_update_scheduled_message does on Neuron

AI agents use neuron_update_scheduled_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 scheduled message to update
`sendAt`	string	—	New ISO 8601 date-time for scheduled delivery (must be in the future)
`message`	string	—	New message text content
`mediaUrl`	string	—	New media URL to attach
`contactName`	string	—	Updated display name for the recipient
`messageType`	string	—	New message type: 'text', 'image', 'audio', 'video', or 'document'

Parameters from the server's own tool schema.

RISK

Why neuron_update_scheduled_message is rated Medium

An AI agent can call neuron_update_scheduled_message faster than any human can review: one bad instruction and it creates or modifies resources in Neuron by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs neuron_update_scheduled_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_update_scheduled_message, this is the rule to start with:

neuron_update_scheduled_message Rate-limited

neuron_update_scheduled_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "neuron_update_scheduled_message": {
      "limits": [
        {
          "counter": "neuron_update_scheduled_message_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Neuron, apply this rule, and every neuron_update_scheduled_message call is checked against it from then on.

FAQ

Questions about neuron_update_scheduled_message

What does the neuron_update_scheduled_message tool do? +

Update the message content, media, or send time of a scheduled message. Only messages with status 'scheduled' can be updated. 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.

What parameters does neuron_update_scheduled_message accept? +

neuron_update_scheduled_message accepts 6 parameters: id, sendAt, message, mediaUrl, contactName, messageType. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on neuron_update_scheduled_message? +

Register the Neuron MCP server in PolicyLayer and add a rule for neuron_update_scheduled_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.

What risk level is neuron_update_scheduled_message? +

neuron_update_scheduled_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit neuron_update_scheduled_message? +

Yes. Add a rate_limit block to the neuron_update_scheduled_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.

How do I block neuron_update_scheduled_message completely? +

Set action: deny in the PolicyLayer policy for neuron_update_scheduled_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.

What MCP server provides neuron_update_scheduled_message? +

neuron_update_scheduled_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.

KEEP EXPLORING

More on Neuron, and thousands of servers like it.

This server

All 281 Neuron tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →