create_calendar_event

SERVERLocal SOURCElocal-mcp

Medium RISK CLASS

Category Write

Parameters 93 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-local-mcp-local-mcp/create-calendar-event.md

WHAT IT DOES

What create_calendar_event does on Local

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

Parameter	Type	Required	Description
`notes`	string	—	Event notes (optional)
`title`	string	Yes	Event title
`confirm`	boolean	—	Must be true to create the event
`calendar`	string	—	Calendar name to match (optional, alternative to calendar_id)
`end_date`	string	Yes	ISO 8601 datetime
`location`	string	—	Location (optional)
`attendees`	array	—	List of email addresses to invite (optional, CalDAV/Exchange only)
`start_date`	string	Yes	ISO 8601 datetime (YYYY-MM-DDTHH:MM:SS)
`calendar_id`	string	—	Calendar UUID from list_calendar_names (optional, defaults to default calendar)

Parameters from the server's own tool schema.

RISK

Why create_calendar_event is rated Medium

This tool creates new calendar data reversibly. It is a Write operation as it adds data to the user's calendar without deletion or irreversible side effects. Severity is medium because calendar event creation could be misused to spam attendees with invitations, create misleading meetings, or interfere with someone's schedule, but the action is reversible (events can be deleted).

From the tool's definition Tool name 'create_calendar_event' and description states it 'Creates an event in the Mac's Calendar app' with required title, start_date, end_date parameters and optional attendee invitations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_calendar_event safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_calendar_event, this is the rule to start with:

create_calendar_event Rate-limited

create_calendar_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": {
    "create_calendar_event": {
      "limits": [
        {
          "counter": "create_calendar_event_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every create_calendar_event call is checked against it from then on.

FAQ

Questions about create_calendar_event

What does the create_calendar_event tool do? +

Creates an event in the Mac's Calendar app (Calendar.app). Requires title, start_date, end_date. Optionally invite attendees by email (CalDAV/Exchange calendars only). For Microsoft 365 use m365_create_event instead. It is categorised as a Write tool in the Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does create_calendar_event accept? +

create_calendar_event accepts 9 parameters: notes, title, confirm, calendar, end_date, location, attendees, start_date, calendar_id. Required: title, end_date, start_date. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_calendar_event? +

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

What risk level is create_calendar_event? +

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

Can I rate-limit create_calendar_event? +

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

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

create_calendar_event is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Local, and thousands of servers like it.

This server

All 234 Local tools →

Across the catalogue

calendar_create_event on Apple Apps MCP →create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →