neuron_update_event

Update a host-created event. Use scope='future' to update all future instances of a recurring series.

SERVERNeuron SOURCEneuron-mcp-server

Medium RISK CLASS

Category Write

Parameters 91 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-event.md

WHAT IT DOES

What neuron_update_event does on Neuron

AI agents use neuron_update_event 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	Event (booking) UUID
`scope`	string	—	'single' (default) or 'future' to update all future instances
`title`	string	—	New title
`endTime`	string	—	New end time (ISO 8601)
`attendees`	array	—	Updated attendee list
`startTime`	string	—	New start time (ISO 8601)
`description`	string	—	New description
`locationType`	string	—	New location type
`locationValue`	string	—	New location value

Parameters from the server's own tool schema.

RISK

Why neuron_update_event is rated Medium

An AI agent can call neuron_update_event 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.

Risk signalsHigh parameter count (14 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

neuron_update_event Rate-limited

neuron_update_event 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_event": {
      "limits": [
        {
          "counter": "neuron_update_event_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_event call is checked against it from then on.

FAQ

Questions about neuron_update_event

What does the neuron_update_event tool do? +

Update a host-created event. Use scope='future' to update all future instances of a recurring series. 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_event accept? +

neuron_update_event accepts 9 parameters: id, scope, title, endTime, attendees, startTime, description, locationType, locationValue. 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_event? +

Register the Neuron MCP server in PolicyLayer and add a rule for neuron_update_event: 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_event? +

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

Can I rate-limit neuron_update_event? +

Yes. Add a rate_limit block to the neuron_update_event 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_event completely? +

Set action: deny in the PolicyLayer policy for neuron_update_event. 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_event? +

neuron_update_event 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 401 Neuron tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

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