mcp__planning__update_calendar_event
更新日程时间或内容。若日程含 nativeOrigin，会写回用户已连接的系统日历；单项修改先确认，批量修改必须明确确认，只读来源会失败。仅 Pi Agent 可用。
This record as markdown: /tools/dutydeck/mcp--planning--update-calendar-event.md
What mcp__planning__update_calendar_event does on DutyDeck
AI agents use mcp__planning__update_calendar_event to create or update resources in DutyDeck, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DutyDeck environment.
Why mcp__planning__update_calendar_event is rated Medium
An AI agent can call mcp__planning__update_calendar_event faster than any human can review: one bad instruction and it creates or modifies resources in DutyDeck by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs mcp__planning__update_calendar_event safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DutyDeck, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mcp__planning__update_calendar_event, this is the rule to start with:
mcp__planning__update_calendar_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 DutyDeck, apply this rule, and every mcp__planning__update_calendar_event call is checked against it from then on.
Questions about mcp__planning__update_calendar_event
更新日程时间或内容。若日程含 nativeOrigin，会写回用户已连接的系统日历；单项修改先确认，批量修改必须明确确认，只读来源会失败。仅 Pi Agent 可用。. It is categorised as a Write tool in the DutyDeck MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DutyDeck MCP server in PolicyLayer and add a rule for mcp__planning__update_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 DutyDeck. Nothing to install.
mcp__planning__update_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 mcp__planning__update_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 mcp__planning__update_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.
mcp__planning__update_calendar_event is provided by the DutyDeck MCP server (taokoplay/DutyDeck). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DutyDeck, and thousands of servers like it.
This server
Across the catalogue