Delete a custom item for an athlete from Intervals.icu Args: item_id: The custom item ID to delete athlete_id: The Intervals.icu athlete ID (optional, will use ATHLETE_ID from .env if not provided) api_key: The Intervals.icu API key (optional, will use API_KEY from .env if not provided)
AI agents call delete_custom_item to permanently remove resources in Intervals Icu MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes custom item records without a stated undo or recovery mechanism. While the blast radius is limited to custom items within a fitness tracking system (not production-critical or financial data), unauthorized deletion could cause data loss for athletes.
From the tool's definition Tool name is 'delete_custom_item' and description states 'Delete a custom item for an athlete from Intervals.icu'.
Documented attack patterns abuse exactly the kind of access delete_custom_item gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Intervals Icu MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_custom_item:
{
"version": "1",
"default": "deny",
"hide": [
"delete_custom_item"
]
}delete_custom_item disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a custom item for an athlete from Intervals.icu Args: item_id: The custom item ID to delete athlete_id: The Intervals.icu athlete ID (optional, will use ATHLETE_ID from .env if not provided) api_key: The Intervals.icu API key (optional, will use API_KEY from .env if not provided). It is categorised as a Destructive tool in the Intervals Icu MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Intervals Icu MCP Server MCP server in PolicyLayer and add a rule for delete_custom_item: 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.
delete_custom_item 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 delete_custom_item 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 delete_custom_item. 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.
delete_custom_item is provided by the Intervals Icu MCP Server MCP server (mvilanova/intervals-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Intervals Icu MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 Intervals Icu MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.