calendar_create_event · Apple Apps MCP: Risk & Policy

WHAT IT DOES

What calendar_create_event does on Apple Apps MCP

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

WHY IT NEEDS A POLICY

Why calendar_create_event needs a policy

This tool creates new data (calendar events) in a reversible manner. The user can delete or modify the event afterward. While calendar events can have downstream effects (e.g., triggering notifications, affecting scheduling), the tool itself performs a standard data creation operation without permanent destruction or financial impact.

From the tool's definition Tool name is 'calendar_create_event' and description states 'Create a calendar event.' The verb 'create' and the action of adding a new calendar event to the user's calendar are characteristic of Write operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

calendar_create_event Rate-limited

calendar_create_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": {
    "calendar_create_event": {
      "limits": [
        {
          "counter": "calendar_create_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 Apps MCP, so you can run agents against it safely.

FAQ

Questions about calendar_create_event

What does the calendar_create_event tool do? +

Create a calendar event. It is categorised as a Write tool in the Apple Apps MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on calendar_create_event? +

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

What risk level is calendar_create_event? +

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

Can I rate-limit calendar_create_event? +

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

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

calendar_create_event is provided by the Apple Apps MCP server (0xatrilla/apple-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.