POST /api/v1/athlete/{id}/events/apply-plan
AI agents use applyPlan to create or update resources in Intervals Icu Api — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Intervals Icu Api environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | |
folder_id | number | — | |
extra_workouts | array | — | |
start_date_local | string | — |
Parameters from the server's own tool schema.
This tool creates or modifies data (applies a plan to events) in a reversible manner. POST operations typically create or update records. While it could have downstream effects on an athlete's schedule, it does not delete data irreversibly or execute arbitrary code. The sibling tools like 'createEvent', 'createFolder', and 'applyToActivities' confirm this server performs Write operations.
From the tool's definition Tool name 'applyPlan' and description 'POST /api/v1/athlete/{id}/events/apply-plan' indicate a POST request that modifies athlete events by applying a training plan.
Risk signalsAccepts file system path (extra_workouts[].attachments[].filename) · Accepts URL/endpoint input (extra_workouts[].attachments[].url) · High parameter count (36 properties)
Attacks that exploit this kind of access
POST /api/v1/athlete/{id}/events/apply-plan. It is categorised as a Write tool in the Intervals Icu Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
applyPlan accepts 4 parameters: id, folder_id, extra_workouts, start_date_local. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Intervals Icu Api MCP server in PolicyLayer and add a rule for applyPlan: 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 Api. Nothing to install.
applyPlan 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 applyPlan 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 applyPlan. 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.
applyPlan is provided by the Intervals Icu Api MCP server (intervals-icu-api-mcp-server). 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 →