Add or update a plain text note (category NOTE) on the Intervals.icu calendar. Args: name: Title of the note description: Plain text content of the note start_date: Date in YYYY-MM-DD format (optional, defaults to today) color: Color of the note (e.g. green, orange, red, blue) athlete_id: The Int...
AI agents use add_or_update_note 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 notes or modifies existing ones reversibly. It does not delete data (that would be Destructive), does not execute code or commands (that would be Execute), and does not involve financial transactions. The severity is medium because an AI agent could create numerous calendar spam entries or overwrite a user's important notes, but the effects are easily reversible by manual deletion or correction.
From the tool's definition Tool description explicitly states 'Add or update a plain text note' on the calendar. The parameters include name, description, start_date, and color for creating or modifying calendar entries. The event_id parameter enables updates to existing notes.
Documented attack patterns abuse exactly the kind of access add_or_update_note 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 add_or_update_note:
{
"version": "1",
"default": "deny",
"tools": {
"add_or_update_note": {
"limits": [
{
"counter": "add_or_update_note_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_or_update_note 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.
Add or update a plain text note (category NOTE) on the Intervals.icu calendar. Args: name: Title of the note description: Plain text content of the note start_date: Date in YYYY-MM-DD format (optional, defaults to today) color: Color of the note (e.g. green, orange, red, blue) athlete_id: The Intervals.icu athlete ID (optional) api_key: The Intervals.icu API key (optional) event_id: The Intervals.icu event ID (optional, for updates). 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 add_or_update_note: 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.
add_or_update_note 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 add_or_update_note 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 add_or_update_note. 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.
add_or_update_note is provided by the Intervals Icu MCP Server MCP server (mvilanova/intervals-mcp-server). 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.
21 Intervals Icu MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.