Create a new calendar event
AI agents use create_event to create or update resources in macOS MCP Servers — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your macOS MCP Servers environment.
Creating calendar events modifies the user's calendar state but is not destructive (events can be deleted), not financial, and does not execute arbitrary code. It falls squarely into Write category. Severity is medium because a compromised AI agent could spam calendar events or create misleading appointments affecting the user's schedule and potentially impacting their time management and business operations.
From the tool's definition Tool name is 'create_event' and description states 'Create a new calendar event' — this creates new data in the calendar system reversibly.
Attacks that exploit this kind of access
Create a new calendar event. It is categorised as a Write tool in the macOS MCP Servers MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the macOS MCP Servers MCP server in PolicyLayer and add a rule for 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 macOS MCP Servers. Nothing to install.
create_event 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 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.
Set action: deny in the PolicyLayer policy for 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.
create_event is provided by the macOS MCP Servers MCP server (tdisawas0github/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 →