m365_create_event
Create a calendar event in your Microsoft 365 / Outlook calendar.
This record as markdown: /tools/com-local-mcp-local-mcp/m365-create-event.md
What m365_create_event does on Local
AI agents use m365_create_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 |
|---|---|---|---|
end | string | Yes | End time in ISO 8601, e.g. '2026-05-20T11:00:00' |
body | string | — | Event description (optional) |
start | string | Yes | Start time in ISO 8601, e.g. '2026-05-20T10:00:00' |
subject | string | Yes | Event title |
calendar | string | — | Calendar name to create the event in — partial, case-insensitive match (optional). Omit to use the primary calendar. |
location | string | — | Location (optional) |
timezone | string | — | IANA timezone, e.g. 'America/New_York' (default: UTC) |
attendees | string | — | Comma-separated email addresses to invite (optional) |
Parameters from the server's own tool schema.
Why m365_create_event is rated Medium
This tool creates new calendar entries, which is a reversible write operation. It modifies user data (calendar) but the action can be undone by deleting the created event. Severity is medium because unauthorized calendar event creation could cause schedule disruption and social engineering attacks, but does not involve financial transactions or irreversible data destruction.
From the tool's definition Tool name 'create_event' and description 'Create a calendar event in your Microsoft 365 / Outlook calendar' indicate creation of new calendar data.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs m365_create_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 m365_create_event, this is the rule to start with:
m365_create_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every m365_create_event call is checked against it from then on.
Questions about m365_create_event
Create a calendar event in your Microsoft 365 / Outlook calendar. 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.
m365_create_event accepts 8 parameters: end, body, start, subject, calendar, location, timezone, attendees. Required: end, start, subject. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for m365_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 Local. Nothing to install.
m365_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 m365_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 m365_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.
m365_create_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.
More on Local, and thousands of servers like it.
This server
Across the catalogue