add_or_update_event

THE RISK

Medium Risk

Why add_or_update_event needs a policy

The tool's name clearly indicates it performs create (add) or modify (update) operations on events in the fitness tracking system. This is a Write operation—data is being created or changed but not permanently destroyed. Severity is medium because misuse could disrupt a user's training schedule or wellness data, but effects are reversible via deletion or re-modification.

From the tool's definition Tool name 'add_or_update_event' indicates creation or modification of event data. Description is empty, limiting confidence.

Documented attack patterns abuse exactly the kind of access add_or_update_event gives an agent:

POLICY

How to control add_or_update_event

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_event:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_or_update_event": {
      "limits": [
        {
          "counter": "add_or_update_event_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

add_or_update_event 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.

Create a free account and register Intervals Icu MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Intervals Icu MCP Server tools

Destructive delete_custom_item Delete a custom item for an athlete from Intervals.icu Args: item_id: The cus Destructive delete_event Delete event for an athlete from Intervals.icu Args: athlete_id: The Intervals Destructive delete_events_by_date_range Delete events for an athlete from Intervals.icu in the specified date range. Args: Execute register_tools Register all MCP tools with the FastMCP server instance. This function imports all to Write add_activity_message Add a message (note/comment) to an activity on Intervals.icu Args: activity_i Write add_or_update_note Add or update a plain text note (category NOTE) on the Intervals.icu calendar. Args: Write create_custom_item create_custom_item Write update_custom_item update_custom_item

All 21 Intervals Icu MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about add_or_update_event

What does the add_or_update_event tool do? +

add_or_update_event. 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.

How do I enforce a policy on add_or_update_event? +

Register the Intervals Icu MCP Server MCP server in PolicyLayer and add a rule for add_or_update_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 Intervals Icu MCP Server. Nothing to install.

What risk level is add_or_update_event? +

add_or_update_event is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_or_update_event? +

Yes. Add a rate_limit block to the add_or_update_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.

How do I block add_or_update_event completely? +

Set action: deny in the PolicyLayer policy for add_or_update_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.

What MCP server provides add_or_update_event? +

add_or_update_event 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.

Enforce policy on every Intervals Icu MCP Server tool call.

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.

CHECK YOUR STACK →