Create a Microsoft calendar event.
AI agents use microsoft_create_calendar_event to create or update resources in Personal Mail — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Personal Mail environment.
This tool creates new calendar events, which is a write operation that modifies the user's calendar state. While calendar event creation is reversible (events can be deleted), it commits the user to a calendar obligation and could be misused by an agent to schedule fraudulent meetings, spam invitations, or disrupt the user's calendar.
From the tool's definition Tool name 'microsoft_create_calendar_event' and description 'Create a Microsoft calendar event' indicate irreversible creation of calendar data.
Attacks that exploit this kind of access
Create a Microsoft calendar event. It is categorised as a Write tool in the Personal Mail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Personal Mail MCP server in PolicyLayer and add a rule for microsoft_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 Personal Mail. Nothing to install.
microsoft_create_calendar_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 microsoft_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.
Set action: deny in the PolicyLayer policy for microsoft_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.
microsoft_create_calendar_event is provided by the Personal Mail MCP server (srogerf/personal-mail-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 →