set_location_alarm · MCP Apple Reminders MCP: Risk & Policy

WHAT IT DOES

What set_location_alarm does on MCP Apple Reminders

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

WHY IT NEEDS A POLICY

Why set_location_alarm needs a policy

This tool modifies reminder configurations by setting location-based alarms—a reversible change to existing reminder metadata. It fits the Write category as it updates reminder state. Severity is medium because misuse could create unwanted alarms or location tracking patterns, but the blast radius is limited to the user's own reminders and does not involve financial transactions or destructive data loss.

From the tool's definition Tool name 'set_location_alarm' combined with server description stating the MCP server enables 'create, read, update, delete' operations on reminders.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_location_alarm Rate-limited

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

FAQ

Questions about set_location_alarm

What does the set_location_alarm tool do? +

set_location_alarm. It is categorised as a Write tool in the MCP 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 set_location_alarm? +

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

What risk level is set_location_alarm? +

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

Can I rate-limit set_location_alarm? +

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

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

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