Update the wellness record for the date (ISO-8601)
AI agents use updateWellness 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 | |
atl | number | — | |
ctl | number | — | |
hrv | number | — | |
date | string | Yes | |
mood | number | — | |
spO2 | number | — | |
steps | number | — | |
injury | number | — | |
locked | boolean | — | |
stress | number | — | |
vo2max | number | — |
Parameters from the server's own tool schema.
This tool modifies wellness data (presumably metrics like sleep, stress, mood, or similar health metrics) for a specific date. Updates are reversible—users can modify the record again later—making this a Write operation rather than Destructive.
From the tool's definition Tool name 'updateWellness' and description 'Update the wellness record for the date' indicate modification of existing data. The verb 'update' is characteristic of Write operations that create or modify data reversibly.
Risk signalsHigh parameter count (52 properties)
Attacks that exploit this kind of access
Update the wellness record for the date (ISO-8601). 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.
updateWellness accepts 12 parameters: id, atl, ctl, hrv, date, mood, spO2, steps, injury, locked, stress, vo2max. Required: id, date. 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 updateWellness: 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.
updateWellness 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 updateWellness 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 updateWellness. 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.
updateWellness 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 →