Update a workout
AI agents use updateWorkout 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 | |
day | number | — | |
days | number | — | |
name | string | — | |
tags | array | — | |
time | string | — | |
type | string | — | |
color | string | — | |
indoor | boolean | — | |
joules | number | — | |
target | string | — | |
body_id | number | — | (body property: id) |
Parameters from the server's own tool schema.
This tool creates or modifies data reversibly—updating a workout record is a Write operation. It is not destructive (does not delete), does not execute external code, and does not involve financial transactions. The severity is medium because misuse could corrupt training data or plans, but the changes are reversible and limited to a single workout record.
From the tool's definition Tool name 'updateWorkout' and description 'Update a workout' indicate modification of existing workout data in the Intervals.icu fitness platform.
Risk signalsAccepts file system path (attachments[].filename) · Accepts URL/endpoint input (attachments[].url) · High parameter count (37 properties)
Attacks that exploit this kind of access
Update a workout. 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.
updateWorkout accepts 12 parameters: id, day, days, name, tags, time, type, color, indoor, joules, target, body_id. Required: id. 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 updateWorkout: 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.
updateWorkout 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 updateWorkout 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 updateWorkout. 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.
updateWorkout 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 →