Search, create, and open calendar events in Apple Calendar app
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 modifies calendar state by creating events, which falls under the Write category (data creation/modification that is reversible). The severity is medium because: (1) calendar event creation is reversible/editable, (2) blast radius is limited to the user's own calendar, (3) misuse could clutter calendars or create misleading scheduling information, but cannot cause financial loss or permanent data…
From the tool's definition Tool description states it can "create, and open calendar events" - creation of calendar events is a write operation that modifies user data reversibly. While it also includes search/read capability, the write functionality is the most severe aspect.
Documented attack patterns abuse exactly the kind of access calendar gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Apple MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for calendar:
{
"version": "1",
"default": "deny",
"tools": {
"calendar": {
"limits": [
{
"counter": "calendar_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}calendar 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.
Free to start. No card required.
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 (jxnl/apple-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Apple MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Apple MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.