update_event
Update fields on an existing calendar event. Only provided fields are modified. Description updates support markdown.
This record as markdown: /tools/dugynoo-huly-mcp/update-event.md
What update_event does on Huly
AI agents use update_event to create or update resources in Huly, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Huly environment.
Why update_event is rated Medium
This tool modifies calendar event data (dates, descriptions, attendees, etc.) in a reversible manner. It qualifies as Write rather than Read (it changes state) or Execute (no code execution or external operations triggered). While calendar events can affect scheduling and notifications, the blast radius is limited to that specific event's metadata.
From the tool's definition update_event updates fields on an existing calendar event, modifying data reversibly. The description explicitly states 'Only provided fields are modified,' indicating a selective update operation without deletion or execution of external code.
Attacks that exploit this kind of access
The rule that runs update_event safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Huly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_event, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every update_event call is checked against it from then on.
Questions about update_event
Update fields on an existing calendar event. Only provided fields are modified. Description updates support markdown. It is categorised as a Write tool in the Huly MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Huly 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 Huly. 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 Huly MCP server (dugynoo/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Huly, and thousands of servers like it.
This server
Across the catalogue