# move_event

Moves an event to a different calendar (changes its organizer calendar; the event id stays the same). Rescheduling to another TIME is update_event, not this. Only regular events can move — Out of Office, Focus Time, working-location and birthday events cannot, and events with attendees can be moved only by their organizer. Needs writer access to both calendars. send_updates=all notifies the guests.

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

## Facts

- Tool: `move_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: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 4 (3 required)
- Recommended policy verdict: Rate-limited

## 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 |
| `destination_calendar_id` | string | yes | The calendar id the event moves to (from list_calendars). |

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": "move_event",
    "arguments": {
      "event_id": "<event_id>",
      "calendar_id": "<calendar_id>",
      "destination_calendar_id": "<destination_calendar_id>"
    }
  }
}
```

## Why move_event is rated Medium

An AI agent can call move_event faster than any human can review: one bad instruction and it creates or modifies resources in Mcp Google Calendar by the hundred, each call as confident as the last.

## Use case

AI agents use move_event to create or update resources in Mcp Google Calendar, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Google Calendar environment.

## Recommended policy (PolicyLayer)

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

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

## Other tools on Mcp Google Calendar (18)

- `delete_event` — Destructive — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/delete-event.md
- `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
- `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