Update an existing Synology Calendar event. Requires confirm=true.
AI agents use calendar_update_event to create or update resources in Synology Office — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Synology Office environment.
This tool creates or modifies calendar data (an event) in a reversible manner. While the description notes a 'confirm=true' requirement suggesting safeguards, the core function is to update/modify existing calendar events, which falls under the Write category.
From the tool's definition Tool name is 'calendar_update_event' and description states 'Update an existing Synology Calendar event.' Update operations modify data reversibly.
Documented attack patterns abuse exactly the kind of access calendar_update_event gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Synology Office, and nothing reaches the server without passing your rules. This is the rule we recommend for calendar_update_event:
{
"version": "1",
"default": "deny",
"tools": {
"calendar_update_event": {
"limits": [
{
"counter": "calendar_update_event_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}calendar_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 Synology Calendar event. Requires confirm=true. It is categorised as a Write tool in the Synology Office MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Synology Office MCP server in PolicyLayer and add a rule for calendar_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 Synology Office. Nothing to install.
calendar_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 calendar_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 calendar_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.
calendar_update_event is provided by the Synology Office MCP server (vocweb/synology-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Synology Office, 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.
39 Synology Office tools catalogued and risk-classified — across an index of 43,000+ MCP servers.