Create an event (planned workout, note etc.) on the athlete's calendar
AI agents use createEvent 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 | |
uid | string | — | |
name | string | — | |
tags | array | — | |
type | string | — | Valid types: Ride, Run, Swim, Walk, Weight Training |
color | string | — | |
p_max | number | — | |
ss_cp | number | — | |
indoor | boolean | — | |
joules | number | — | |
target | string | — | |
body_id | number | — | (body property: id) |
Parameters from the server's own tool schema.
This tool creates new calendar events, which is a reversible write operation. The severity is high because an AI agent misusing this could flood an athlete's calendar with unwanted events, disrupting their training plan and workflow. However, it is not Destructive since events can be deleted, and not Execute since it doesn't run arbitrary code. Write is the appropriate category.
From the tool's definition Tool name 'createEvent' and description states it will 'Create an event (planned workout, note etc.) on the athlete's calendar' — a direct data creation operation.
Risk signalsAccepts file system path (attachments[].filename) · Accepts URL/endpoint input (attachments[].url) · High parameter count (105 properties)
Attacks that exploit this kind of access
Create an event (planned workout, note 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.
createEvent accepts 12 parameters: id, uid, name, tags, type, color, p_max, ss_cp, indoor, joules, target, body_id. 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 createEvent: 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.
createEvent 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 createEvent 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 createEvent. 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.
createEvent 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 →