# delete_event

Deletes (cancels) an event — there is no undelete. Deleting a series master id cancels the ENTIRE recurring series; deleting one instance id (from list_event_instances) cancels only that occurrence. On an event with guests this cancels the meeting for everyone, but cancellation emails go out only with send_updates=all. Returns {deleted:true}.

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

## Facts

- Tool: `delete_event`
- Server: Mcp Google Calendar (`@a1-x-tech/mcp-google-calendar`) — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar.md
- Install: `npx -y @a1-x-tech/mcp-google-calendar`
- Homepage: https://github.com/A1-x-Tech/mcp-google-calendar
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 3 (2 required)
- Recommended policy verdict: Hidden

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `event_id` | string | yes | The event id from list_events or create_event output. A recurring-instance id (masterId_20260101T100000Z from list_event_instances) addresses one occurrence. |
| `calendar_id` | string | yes | The calendar id from list_calendars, or "primary" for the authenticated user's main calendar. |
| `send_updates` | string | no | Who receives an email about this change: all guests, only guests outside your organization, or nobody. Defaults to none — attendees are NOT notified unless you |

Parameters from the server's own tool schema.

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

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

## Why delete_event is rated Critical

An AI agent that decides to call delete_event doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Mcp Google Calendar is gone. There is no undo for destructive operations.

Risk signals: Bulk/mass operation — affects multiple targets

## Use case

AI agents call delete_event to permanently remove resources in Mcp Google 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 Mcp Google Calendar:

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

## Other tools on Mcp Google Calendar (18)

- `logout` — Destructive — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/logout.md
- `start_login` — Execute — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/start-login.md
- `auth_status` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/auth-status.md
- `get_calendar` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/get-calendar.md
- `get_event` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/get-event.md
- `list_calendars` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/list-calendars.md
- `list_event_instances` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/list-event-instances.md
- `list_events` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/list-events.md
- `query_free_busy` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/query-free-busy.md
- `raw_request` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/raw-request.md
- `create_event` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/create-event.md
- `create_focus_time` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/create-focus-time.md
- `create_out_of_office` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/create-out-of-office.md
- `finish_login` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/finish-login.md
- `move_event` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/move-event.md
- `set_client` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/set-client.md
- `setup_instructions` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/setup-instructions.md
- `update_event` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/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=a1-x-tech-mcp-google-calendar · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/a1-x-tech-mcp-google-calendar