Create multiple events (planned workouts, notes etc.) on the athlete's calendar
AI agents use createMultipleEvents 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 | |
upsert | boolean | — | Update events with matching external_id and created by the same OAuth application instead of creating new ones |
upsertOnUid | boolean | Yes | Update events with matching uid instead of creating new ones, ignored if upsert=true. For Events with category=TARGET existing matching targets for the date and |
updatePlanApplied | boolean | Yes | Give all events created or updated the same new plan_applied date (now) |
Parameters from the server's own tool schema.
This tool creates calendar events in bulk, which is a reversible write operation. While it modifies the athlete's schedule data, it does not delete, destroy, or execute arbitrary code. The 'multiple' aspect increases the blast radius slightly (an agent could spam many events), justifying medium severity rather than low.
From the tool's definition Tool name 'createMultipleEvents' and description state it "Create[s] multiple events (planned workouts, notes etc.) on the athlete's calendar" — a write operation that adds data to a calendar.
Attacks that exploit this kind of access
Create multiple events (planned workouts, notes etc.) on the athlete's calendar. 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.
createMultipleEvents accepts 4 parameters: id, upsert, upsertOnUid, updatePlanApplied. Required: id, upsertOnUid, updatePlanApplied. 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 createMultipleEvents: 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.
createMultipleEvents 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 createMultipleEvents 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 createMultipleEvents. 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.
createMultipleEvents 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 →