Update/create an interval
AI agents use updateInterval 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 | |
gap | number | — | |
type | string | — | |
zone | number | — | |
label | string | — | |
ss_cp | number | — | |
joules | number | — | |
body_id | number | — | (body property: id) |
distance | number | — | |
end_time | number | — | |
group_id | string | — | |
ss_p_max | number | — |
Parameters from the server's own tool schema.
This tool creates or modifies interval records, which are core data objects in a training platform. The action is reversible (intervals can be deleted or re-edited), so it falls under Write rather than Destructive.
From the tool's definition Tool name is 'updateInterval' with description 'Update/create an interval'. The use of 'update/create' indicates reversible modification of interval data within a fitness/training tracking system (Intervals.icu).
Risk signalsHigh parameter count (77 properties)
Attacks that exploit this kind of access
Update/create an interval. 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.
updateInterval accepts 12 parameters: id, gap, type, zone, label, ss_cp, joules, body_id, distance, end_time, group_id, ss_p_max. 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 updateInterval: 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.
updateInterval 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 updateInterval 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 updateInterval. 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.
updateInterval 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 →