intervals_create_gear
AI agents use intervals_create_gear 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 creates gear records in Intervals.icu, which modifies user data but is reversible (gear can be deleted or updated). The lack of description lowers confidence slightly, but the naming pattern and context from sibling tools clearly indicate a Write operation. Severity is medium because incorrect gear creation could clutter user data and require manual cleanup, but poses no financial or destructive risk.
From the tool's definition Tool name 'intervals_create_gear' indicates creation of a new resource ('create_' prefix) within the Intervals.icu fitness service. The server description confirms Intervals.icu integration for activity/workout data.
Attacks that exploit this kind of access
intervals_create_gear. 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_create_gear: 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_create_gear 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_create_gear 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_create_gear. 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_create_gear 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 →