# delete_event

Deletes an event.

Agent View of the PolicyLayer registry record for `delete_event`. HTML page: https://policylayer.com/tools/deciduus-calendar-mcp/delete-event

## Facts

- Tool: `delete_event`
- Server: Calendar (`deciduus/calendar-mcp`) — https://policylayer.com/tools/deciduus-calendar-mcp.md
- Homepage: https://github.com/deciduus/calendar-mcp
- Risk category: Destructive (Critical risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

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

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

## Why delete_event is rated Critical

The tool permanently removes calendar events without possibility of recovery through normal means. While not as critical as financial or system-level data deletion, calendar events represent user commitments and plans. Accidental or malicious deletion could cause significant disruption to business operations, meetings, and personal schedules. The destructive nature places it above Write or Execute categories.

From the tool's own definition: "Tool name 'delete_event' with description 'Deletes an event.' directly indicates irreversible removal of calendar data."

## Use case

AI agents call delete_event to permanently remove resources in Calendar, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_event"
  ]
}
```

## Other tools on Calendar (11)

- `analyze_busyness` — Read — https://policylayer.com/tools/deciduus-calendar-mcp/analyze-busyness.md
- `check_attendee_status` — Read — https://policylayer.com/tools/deciduus-calendar-mcp/check-attendee-status.md
- `find_events` — Read — https://policylayer.com/tools/deciduus-calendar-mcp/find-events.md
- `list_calendars` — Read — https://policylayer.com/tools/deciduus-calendar-mcp/list-calendars.md
- `query_free_busy` — Read — https://policylayer.com/tools/deciduus-calendar-mcp/query-free-busy.md
- `add_attendee` — Write — https://policylayer.com/tools/deciduus-calendar-mcp/add-attendee.md
- `create_calendar` — Write — https://policylayer.com/tools/deciduus-calendar-mcp/create-calendar.md
- `create_event` — Write — https://policylayer.com/tools/deciduus-calendar-mcp/create-event.md
- `quick_add_event` — Write — https://policylayer.com/tools/deciduus-calendar-mcp/quick-add-event.md
- `schedule_mutual` — Write — https://policylayer.com/tools/deciduus-calendar-mcp/schedule-mutual.md
- `update_event` — Write — https://policylayer.com/tools/deciduus-calendar-mcp/update-event.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=deciduus-calendar-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/deciduus-calendar-mcp
