intervals_get_wellness
AI agents call intervals_get_wellness to retrieve information from FitnessMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears designed to query or fetch wellness metrics from the Intervals.icu service. 'Get' operations are non-destructive reads. While the empty description reduces confidence slightly, the consistent naming pattern across the sibling tools and the server's stated purpose of enabling 'data access' (read-oriented) supports the Read classification.
From the tool's definition Tool name 'intervals_get_wellness' contains 'get', a classic Read operation verb. No description provided, but the naming convention and context within a fitness data aggregation server (alongside other data retrieval tools like cronometer_get_daily_nutrition…
Attacks that exploit this kind of access
intervals_get_wellness. It is categorised as a Read tool in the FitnessMCP MCP Server, which means it retrieves data without modifying state.
Register the Fitness MCP server in PolicyLayer and add a rule for intervals_get_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 FitnessMCP. Nothing to install.
intervals_get_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 intervals_get_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 intervals_get_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.
intervals_get_wellness is provided by the Fitness MCP server (senoj100-alt/fitnessmcp). 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 →