AI agents use createEvent to create or update resources in Outlook — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Outlook environment.
Creating calendar events is a reversible write operation that modifies user data (calendar state) without permanent deletion or financial impact. Severity is medium because malicious event creation could cause scheduling disruption and social engineering risks (fake meeting invitations), but the action is recoverable and doesn't access sensitive personal data or execute arbitrary code.
From the tool's definition Tool name 'createEvent' combined with server purpose (Outlook calendar access). No description provided, but context indicates calendar manipulation capability.
Attacks that exploit this kind of access
createEvent. It is categorised as a Write tool in the Outlook MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Outlook MCP server in PolicyLayer and add a rule for createEvent: 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 Outlook. Nothing to install.
createEvent 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 createEvent 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 createEvent. 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.
createEvent is provided by the Outlook MCP server (lihaokun/outlook-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 →