move_event · Google Calendar MCP: Risk & Policy

WHAT IT DOES

What move_event does on Google Calendar MCP

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

WHY IT NEEDS A POLICY

Why move_event needs a policy

Moving an event between calendars is a write operation that modifies event metadata (calendar location) but is fully reversible. It does not delete data (which would be Destructive) or execute arbitrary code (which would be Execute). The severity is medium because misuse could disorganize a user's calendar workflow, but the impact is limited in scope and can be undone by moving the event again.

From the tool's definition Tool description states 'Move an event to a different calendar', which modifies the calendar assignment of an existing event. This is a reversible change: events can be moved back to their original calendar.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Google Calendar MCP, so you can run agents against it safely.

FAQ

Questions about move_event

What does the move_event tool do? +

Move an event to a different calendar. It is categorised as a Write tool in the Google Calendar MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on move_event? +

Register the 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 Google Calendar MCP. 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 Google Calendar MCP server (paytience/google-calendar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.