GOOGLECALENDAR_EVENTS_MOVE

Moves an event to another calendar, i.e., changes an event's organizer.

Accepts file system path (destination)

Part of the Google Calendar MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

// WHEN AI AGENTS USE THIS TOOL

AI agents use GOOGLECALENDAR_EVENTS_MOVE to create or modify resources in Google Calendar. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON GOOGLECALENDAR_EVENTS_MOVE

Without a policy, an AI agent could call GOOGLECALENDAR_EVENTS_MOVE repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Google Calendar.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

google-calendar.yaml

tools:
  GOOGLECALENDAR_EVENTS_MOVE:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Google Calendar policy for all 29 tools.

// DETAILS

Tool Name GOOGLECALENDAR_EVENTS_MOVE

Category Write

MCP Server Google Calendar MCP Server

Risk Level Medium

// MORE GOOGLE CALENDAR TOOLS

Destructive GOOGLECALENDAR_CALENDARS_DELETE Destructive GOOGLECALENDAR_CLEAR_CALENDAR Destructive GOOGLECALENDAR_DELETE_EVENT Destructive GOOGLECALENDAR_REMOVE_ATTENDEE Write GOOGLECALENDAR_ACL_PATCH Write GOOGLECALENDAR_CALENDARS_UPDATE Write GOOGLECALENDAR_CREATE_EVENT Write GOOGLECALENDAR_PATCH_CALENDAR

View all 29 tools →

// WHAT CAN GO WRONG

Agents calling write-class tools like GOOGLECALENDAR_EVENTS_MOVE have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER WRITE TOOLS ACROSS MCP SERVERS

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

AbraFlexi contact_create AbraFlexi contact_update AbraFlexi evidence_create AbraFlexi evidence_update AbraFlexi invoice_issued_update AbraFlexi invoice_received_create

// RELATED READING

// FAQ

What does the GOOGLECALENDAR_EVENTS_MOVE tool do? +

Moves an event to another calendar, i.e., changes an event's organizer.. It is categorised as a Write tool in the Google Calendar MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on GOOGLECALENDAR_EVENTS_MOVE? +

Add a rule in your Intercept YAML policy under the tools section for GOOGLECALENDAR_EVENTS_MOVE. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Google Calendar MCP server.

What risk level is GOOGLECALENDAR_EVENTS_MOVE? +

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

Can I rate-limit GOOGLECALENDAR_EVENTS_MOVE? +

Yes. Add a rate_limit block to the GOOGLECALENDAR_EVENTS_MOVE rule in your Intercept 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 GOOGLECALENDAR_EVENTS_MOVE completely? +

Set action: deny in the Intercept policy for GOOGLECALENDAR_EVENTS_MOVE. 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 GOOGLECALENDAR_EVENTS_MOVE? +

GOOGLECALENDAR_EVENTS_MOVE is provided by the Google Calendar MCP server (google-cal-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

GOOGLECALENDAR_EVENTS_MOVE

Enforce policies on Google Calendar