Update all events for a date range at once. Only hide_from_athlete and athlete_cannot_edit can be updated
AI agents use updateEvents to create or update resources in Intervals Icu Api — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Intervals Icu Api environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | |
uid | string | — | |
name | string | — | |
tags | array | — | |
type | string | — | Valid types: Ride, Run, Swim, Walk, Weight Training |
color | string | — | |
p_max | number | — | |
ss_cp | number | — | |
indoor | boolean | — | |
joules | number | — | |
newest | string | Yes | Local date (ISO-8601) of newest event to update (inclusive) |
oldest | string | Yes | Local date (ISO-8601) of oldest event to update |
Parameters from the server's own tool schema.
This tool modifies data (event visibility and editability flags) but does so reversibly—both fields can be toggled back. The blast radius is medium: an agent could hide training events from athletes or lock them from editing, disrupting coaching workflows, but the changes are not destructive or financial, and the scope is limited to event metadata rather than core data or code execution.
From the tool's definition Tool description states "Update all events for a date range at once" with modifiable fields "hide_from_athlete and athlete_cannot_edit". These are metadata modifications to existing records, not deletions or irreversible changes.
Risk signalsAccepts file system path (attachments[].filename) · Accepts URL/endpoint input (attachments[].url) · High parameter count (70 properties)
Attacks that exploit this kind of access
Update all events for a date range at once. Only hide_from_athlete and athlete_cannot_edit can be updated. It is categorised as a Write tool in the Intervals Icu Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
updateEvents accepts 12 parameters: id, uid, name, tags, type, color, p_max, ss_cp, indoor, joules, newest, oldest. Required: id, newest, oldest. The full parameter table on this page comes from the server's own tool schema.
Register the Intervals Icu Api MCP server in PolicyLayer and add a rule for updateEvents: 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 Intervals Icu Api. Nothing to install.
updateEvents 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 updateEvents 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 updateEvents. 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.
updateEvents is provided by the Intervals Icu Api MCP server (intervals-icu-api-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →