Update a wellness record, id is the day (ISO-8601)
AI agents use updateWellness_1 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 | — | |
mood | number | — | |
spO2 | number | — | |
steps | number | — | |
injury | number | — | |
locked | boolean | — | |
stress | number | — | |
vo2max | number | — | |
weight | number | — |
Parameters from the server's own tool schema.
This tool creates or modifies data (wellness records) reversibly without deleting or executing arbitrary code. It fits the Write category: data can be updated and changes are not permanently destructive.
From the tool's definition Tool name and description indicate 'Update a wellness record' — this modifies existing data. The parameter 'id is the day (ISO-8601)' shows it targets a specific wellness entry for modification.
Risk signalsHigh parameter count (51 properties)
Attacks that exploit this kind of access
Update a wellness record, id is the day (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_1 accepts 12 parameters: id, atl, ctl, hrv, mood, spO2, steps, injury, locked, stress, vo2max, weight. 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 updateWellness_1: 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_1 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_1 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_1. 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_1 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 →