move_event · Apple Calendar MCP Server MCP: Risk & Policy

WHAT IT DOES

What move_event does on Apple Calendar MCP Server

AI agents use move_event to create or update resources in Apple Calendar MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apple Calendar MCP Server environment.

WHY IT NEEDS A POLICY

Why move_event needs a policy

This is a Write operation because it modifies an existing calendar entry (changes which calendar it belongs to) rather than creating, deleting, or executing arbitrary logic. The change is reversible and does not permanently destroy data. Even if an agent moves events to unintended calendars, the event data persists and can be corrected.

From the tool's definition Tool moves an event to a different calendar, which modifies the location/state of existing data without deleting or creating it. The action is reversible by moving the event back.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_event Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "move_event": {
      "limits": [
        {
          "counter": "move_event_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 Apple Calendar MCP Server, so you can run agents against it safely.

FAQ

Questions about move_event

What does the move_event tool do? +

Move an event to a different calendar. It is categorised as a Write tool in the Apple Calendar 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 move_event? +

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

What risk level is move_event? +

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

Can I rate-limit move_event? +

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

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

move_event is provided by the Apple Calendar MCP Server MCP server (null-phnix/apple-calendar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.