intervals_create_event
AI agents use intervals_create_event to create or update resources in FitnessMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FitnessMCP environment.
The 'create' prefix strongly suggests this tool writes data (creates a new event in Intervals.icu). The lack of description is a limitation, but contextually it aligns with other 'create_*' tools on the server (create_exercise_template, create_routine, create_workout) which modify user fitness data. Event creation is reversible (events can typically be deleted), so it falls under Write rather than Destructive.
From the tool's definition Tool name contains 'create_event' and is part of FitnessMCP's Intervals.icu integration. The 'create' verb indicates data creation/modification. No description provided, limiting specificity.
Attacks that exploit this kind of access
intervals_create_event. It is categorised as a Write tool in the FitnessMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fitness MCP server in PolicyLayer and add a rule for intervals_create_event: 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 FitnessMCP. Nothing to install.
intervals_create_event 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 intervals_create_event 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 intervals_create_event. 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.
intervals_create_event is provided by the Fitness MCP server (senoj100-alt/fitnessmcp). 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 →