AI agents use update_event to create or update resources in Outlook Calendar MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Outlook Calendar MCP environment.
The tool modifies calendar event data (title, time, attendees, etc.) but does not delete or create new events, placing it in the Write category. Severity is medium because calendar updates could cause scheduling conflicts, missed meetings, or confusion among attendees if misused by an AI agent, but the changes are reversible via manual correction or undo operations.
From the tool's definition Tool name 'update_event' and description 'Update an existing calendar event' indicate modification of existing data. Sibling tools include 'delete_event' (destructive) and 'create_event' (write), contextualizing this as a reversible modification.
Documented attack patterns abuse exactly the kind of access update_event gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Outlook Calendar MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for update_event:
{
"version": "1",
"default": "deny",
"tools": {
"update_event": {
"limits": [
{
"counter": "update_event_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_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.
Free to start. No card required.
Update an existing calendar event. It is categorised as a Write tool in the Outlook Calendar MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Outlook Calendar MCP server in PolicyLayer and add a rule for update_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 Outlook Calendar MCP. Nothing to install.
update_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 update_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 update_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.
update_event is provided by the Outlook Calendar MCP server (merajmehrabi/outlook_calendar_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Outlook Calendar MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Outlook Calendar MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.