move_event

SERVERMcp Google Calendar SOURCE@a1-x-tech/mcp-google-calendar

Medium RISK CLASS

Category Write

Parameters 43 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/a1-x-tech-mcp-google-calendar/move-event.md

WHAT IT DOES

What move_event does on Mcp Google Calendar

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.

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	—	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.

RISK

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs move_event safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Google Calendar, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For move_event, this is the rule to start with:

move_event Rate-limited

move_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.

View as policy code

policy.json

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

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Google Calendar, apply this rule, and every move_event call is checked against it from then on.

FAQ

Questions about move_event

What does the move_event tool do? +

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. It is categorised as a Write tool in the Mcp Google Calendar MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does move_event accept? +

move_event accepts 4 parameters: event_id, calendar_id, send_updates, destination_calendar_id. Required: event_id, calendar_id, destination_calendar_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on move_event? +

Register the Mcp Google Calendar MCP server in PolicyLayer and add a rule for move_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 Mcp Google Calendar. Nothing to install.

What risk level is move_event? +

move_event is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit move_event? +

Yes. Add a rate_limit block to the move_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.

How do I block move_event completely? +

Set action: deny in the PolicyLayer policy for move_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.

What MCP server provides move_event? +

move_event is provided by the Mcp Google Calendar MCP server (@a1-x-tech/mcp-google-calendar). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Google Calendar, and thousands of servers like it.

This server

All 19 Mcp Google Calendar tools →

Across the catalogue

move-task on Kanban MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →