Create an event for the current athlete, optionally including intervals in the Native Intervals.icu Workout Format.
AI agents use createEvent to create or update resources in Intervals Icu MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Intervals Icu MCP Server environment.
This tool creates new training event records in the Intervals.icu system. While creation is reversible (events can be deleted via deleteBulkEvents or deleteEvent), it modifies athlete training data which is valuable to the user.
From the tool's definition Tool name is 'createEvent' and description states it will 'Create an event for the current athlete, optionally including intervals'. The verb 'Create' indicates data modification.
Documented attack patterns abuse exactly the kind of access createEvent 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 createEvent:
{
"version": "1",
"default": "deny",
"tools": {
"createEvent": {
"limits": [
{
"counter": "createevent_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}createEvent stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create an event for the current athlete, optionally including intervals in the Native Intervals.icu Workout Format. It is categorised as a Write tool in the Intervals Icu MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Intervals Icu MCP Server 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 MCP Server. 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 MCP Server MCP server (mrgeorgegray/intervals-icu-mcp). 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.
10 Intervals Icu MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.