applyCurrentPlanChanges · Intervals Icu Api MCP

WHAT IT DOES

What applyCurrentPlanChanges does on Intervals Icu Api

AI agents use applyCurrentPlanChanges 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

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why applyCurrentPlanChanges needs a policy

This tool modifies an athlete's calendar by applying plan changes—a reversible write operation. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or move money (would be Financial). The medium severity reflects that calendar modifications could disrupt an athlete's training schedule, but the operation is reversible via subsequent edits or plan adjustments.

From the tool's definition Tool name 'applyCurrentPlanChanges' and description 'Apply any changes from the athlete's current plan to the athlete's calendar' indicate modification of calendar data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

applyCurrentPlanChanges Rate-limited

applyCurrentPlanChanges 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": {
    "applyCurrentPlanChanges": {
      "limits": [
        {
          "counter": "applycurrentplanchanges_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 applyCurrentPlanChanges

What does the applyCurrentPlanChanges tool do? +

Apply any changes from the athlete's current plan to the athlete's calendar. 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 applyCurrentPlanChanges accept? +

applyCurrentPlanChanges accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on applyCurrentPlanChanges? +

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

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

Can I rate-limit applyCurrentPlanChanges? +

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

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

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