intervals_update_sport_settings
AI agents use intervals_update_sport_settings to create or update resources in FitnessMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FitnessMCP environment.
This tool modifies sport settings in Intervals.icu, a fitness tracking service. While 'update' suggests the change is reversible (distinguishing it from Destructive), it alters user configuration. Severity is medium because misuse could corrupt training plans or settings, but the blast radius is limited to one user's sport configuration in a fitness context.
From the tool's definition Tool name 'intervals_update_sport_settings' contains 'update', which modifies configuration data in the Intervals.icu service.
Attacks that exploit this kind of access
intervals_update_sport_settings. It is categorised as a Write tool in the FitnessMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fitness MCP server in PolicyLayer and add a rule for intervals_update_sport_settings: 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_update_sport_settings 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 intervals_update_sport_settings 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_update_sport_settings. 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_update_sport_settings 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 →