move-event · Google Calendar MCP Server MCP: Risk & Policy

WHAT IT DOES

What move-event does on Google Calendar MCP Server

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

WHY IT NEEDS A POLICY

Why move-event needs a policy

Moving an event between calendars is a reversible modification of event metadata/calendar assignment. It does not delete data (would be Destructive) nor execute external code (would be Execute). The blast radius is medium because an agent could unintentionally reorganize a user's calendar structure, but the action is undoable by moving the event back or using undo functionality.

From the tool's definition Tool description states 'Move an event from one calendar to another', which modifies the calendar structure by changing an event's location/calendar assignment.

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 Server, so you can run agents against it safely.

FAQ

Questions about move-event

What does the move-event tool do? +

Move an event from one calendar to another. It is categorised as a Write tool in the Google Calendar MCP Server 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 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 Server. 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 MCP server (progrmoiz/cal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.