# update_event

Update fields on an existing calendar event. Only provided fields are modified. Description updates support markdown.

Agent View of the PolicyLayer registry record for `update_event`. HTML page: https://policylayer.com/tools/dugynoo-huly-mcp/update-event

## Facts

- Tool: `update_event`
- Server: Huly (`dugynoo/huly-mcp`) — https://policylayer.com/tools/dugynoo-huly-mcp.md
- Homepage: https://github.com/dugynoo/huly-mcp
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "update_event",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Huly:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_event": {
      "limits": [
        {
          "counter": "update_event_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Huly (217)

- `dedup_planner_todos` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/dedup-planner-todos.md
- `delete_attachment` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/delete-attachment.md
- `delete_card` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/delete-card.md
- `delete_channel` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/delete-channel.md
- `delete_channel_message` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/delete-channel-message.md
- `delete_comment` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/delete-comment.md
- `delete_component` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/delete-component.md
- `delete_dm_message` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/delete-dm-message.md
- `delete_document` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/delete-document.md
- `delete_event` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/delete-event.md
- `delete_issue` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/delete-issue.md
- `delete_issue_template` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/delete-issue-template.md
- `delete_label` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/delete-label.md
- `delete_milestone` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/delete-milestone.md
- `delete_notification` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/delete-notification.md
- `delete_organization` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/delete-organization.md
- `delete_person` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/delete-person.md
- `delete_project` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/delete-project.md
- `delete_relation` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/delete-relation.md
- `delete_tag_category` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/delete-tag-category.md
- `delete_teamspace` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/delete-teamspace.md
- `delete_test_case` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/delete-test-case.md
- `delete_test_plan` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/delete-test-plan.md
- `delete_test_result` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/delete-test-result.md
- `delete_test_run` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/delete-test-run.md
- `delete_test_suite` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/delete-test-suite.md
- `delete_thread_reply` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/delete-thread-reply.md
- `delete_workspace` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/delete-workspace.md
- `remove_issue_relation` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/remove-issue-relation.md
- `remove_organization_member` — Destructive — https://policylayer.com/tools/dugynoo-huly-mcp/remove-organization-member.md
- …and 187 more: https://policylayer.com/tools/dugynoo-huly-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=dugynoo-huly-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dugynoo-huly-mcp