AI agents use calendar to create or update resources in Apple MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apple MCP environment.
This tool allows creation of calendar events, which is a reversible modification of user data. Although not destructive (events can be deleted), creating events on a user's calendar without proper authorization could cause calendar spam, missed meetings, or scheduling conflicts.
From the tool's definition Tool description states 'create, and open calendar events' - the create action modifies calendar data by adding new events. While search and open are read-like operations, the presence of create capability makes this a Write tool.
Attacks that exploit this kind of access
Search, create, and open calendar events in Apple Calendar app. It is categorised as a Write tool in the Apple MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Apple MCP server in PolicyLayer and add a rule for calendar: 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 MCP. Nothing to install.
calendar is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the calendar 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.
Set action: deny in the PolicyLayer policy for calendar. 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.
calendar is provided by the Apple MCP server (obisagno/apple-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →