intervals_delete_gear
AI agents call intervals_delete_gear to permanently remove resources in FitnessMCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool name 'intervals_delete_gear' directly indicates deletion of gear records from the Intervals.icu service. Deletion is irreversible and destructive, even though the blast radius is limited to personal fitness equipment records rather than broader system or financial data. No description is provided, which slightly lowers confidence, but the verb 'delete' is unambiguous.
From the tool's definition Tool name contains 'delete' which indicates irreversible removal of data. The 'intervals' prefix indicates it operates on Intervals.icu fitness platform data.
Attacks that exploit this kind of access
intervals_delete_gear. It is categorised as a Destructive tool in the FitnessMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Fitness MCP server in PolicyLayer and add a rule for intervals_delete_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_delete_gear is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the intervals_delete_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_delete_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_delete_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 →