apple_reminders_move · Apple Reminders MCP: Risk & Policy

WHAT IT DOES

What apple_reminders_move does on Apple Reminders

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

WHY IT NEEDS A POLICY

Why apple_reminders_move needs a policy

Moving a reminder between lists is a metadata modification that changes the organizational structure of the reminder but does not delete data, execute code, trigger financial transactions, or perform destructive operations. It is fully reversible by moving the reminder back. This fits the Write category (creates or modifies data reversibly).

From the tool's definition Tool description states it "Move[s] a reminder from one list to another" and "preserving all its properties." This is a reversible modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

apple_reminders_move Rate-limited

apple_reminders_move 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": {
    "apple_reminders_move": {
      "limits": [
        {
          "counter": "apple_reminders_move_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 Reminders, so you can run agents against it safely.

FAQ

Questions about apple_reminders_move

What does the apple_reminders_move tool do? +

Move a reminder from one list to another. This tool moves a reminder to a different list while preserving all its properties including due dates, priority, and completion status. Args: - id (string, required): The reminder. It is categorised as a Write tool in the Apple Reminders MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on apple_reminders_move? +

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

What risk level is apple_reminders_move? +

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

Can I rate-limit apple_reminders_move? +

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

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

apple_reminders_move is provided by the Apple Reminders MCP server (mggrim/apple-reminders-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.