markEventAsDone · Intervals Icu Api MCP: Risk & Policy

WHAT IT DOES

What markEventAsDone does on Intervals Icu Api

AI agents use markEventAsDone 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.

PARAMETERS

Parameter	Type	Required	Description
`id`	string	Yes
`eventId`	number	Yes

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why markEventAsDone needs a policy

This tool creates a new manual activity record in the Intervals.icu system, which is a reversible write operation. It modifies the user's activity log by adding a new entry, but does not permanently delete or execute arbitrary code.

From the tool's definition Tool name 'markEventAsDone' and description 'Create a manual activity to match a planned workout' indicate creation of a new data record (manual activity). The verb 'Create' in the description is explicit.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

markEventAsDone Rate-limited

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

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Intervals Icu Api, so you can run agents against it safely.

FAQ

Questions about markEventAsDone

What does the markEventAsDone tool do? +

Create a manual activity to match a planned workout. 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.

What parameters does markEventAsDone accept? +

markEventAsDone accepts 2 parameters: id, eventId. Required: id, eventId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on markEventAsDone? +

Register the Intervals Icu Api MCP server in PolicyLayer and add a rule for markEventAsDone: 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.

What risk level is markEventAsDone? +

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

Can I rate-limit markEventAsDone? +

Yes. Add a rate_limit block to the markEventAsDone 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 markEventAsDone completely? +

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

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