AI agents use createCalendar to create or update resources in MCP Apple Calendars — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Apple Calendars environment.
Creating a calendar is a reversible write operation—it adds new data that can be deleted or modified later. It does not execute arbitrary code, delete data irreversibly, or move money. Severity is medium because misuse could create unwanted calendars or clutter, but the impact is containable and reversible.
From the tool's definition Tool named 'createCalendar' on a calendar manipulation server; sibling tools include deleteCalendar, updateCalendarEvent, indicating this server performs calendar data creation and modification.
Documented attack patterns abuse exactly the kind of access createCalendar gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Apple Calendars, and nothing reaches the server without passing your rules. This is the rule we recommend for createCalendar:
{
"version": "1",
"default": "deny",
"tools": {
"createCalendar": {
"limits": [
{
"counter": "createcalendar_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}createCalendar 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.
createCalendar. It is categorised as a Write tool in the MCP Apple Calendars MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Apple Calendars MCP server in PolicyLayer and add a rule for createCalendar: 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 Calendars. Nothing to install.
createCalendar 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 createCalendar 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 createCalendar. 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.
createCalendar is provided by the MCP Apple Calendars MCP server (shadowfax92/apple-calendar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Apple Calendars, 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.
7 MCP Apple Calendars tools catalogued and risk-classified — across an index of 43,000+ MCP servers.