List wellness data (sleep, fatigue, etc.) for the athlete within a date range.
AI agents call list_wellness to retrieve information from Intervals Icu MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves wellness metrics (sleep, fatigue) for a given date range. It has no side effects—it does not create, modify, delete, or execute operations. It is a straightforward data retrieval operation, fitting the Read category.
From the tool's definition Tool name and description indicate retrieval only: 'List wellness data (sleep, fatigue, etc.)' with 'list' verb and 'for the athlete within a date range' showing query parameters. No modification, deletion, or execution keywords present.
Attacks that exploit this kind of access
List wellness data (sleep, fatigue, etc.) for the athlete within a date range. It is categorised as a Read tool in the Intervals Icu MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Intervals Icu MCP Server MCP server in PolicyLayer and add a rule for list_wellness: 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 MCP Server. Nothing to install.
list_wellness is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_wellness 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 list_wellness. 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.
list_wellness is provided by the Intervals Icu MCP Server MCP server (moxus/intervals-icu-mcp-ts). 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 →