GOOGLESUPER_EVENTS_MOVE

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

SERVERGoogle Super SOURCEgooglesuper

Medium RISK CLASS

Category Write

Parameters 40 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/googlesuper/googlesuper-events-move.md

WHAT IT DOES

What GOOGLESUPER_EVENTS_MOVE does on Google Super

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

Parameter	Type	Required	Description
`event_id`	string	—	Event identifier. To retrieve event identifiers call the events.list method.
`calendar_id`	string	—	Calendar identifier of the source calendar. To retrieve calendar IDs call the calendarList.list method. If you want to access the primary calendar of the curren
`destination`	string	—	Calendar identifier of the destination calendar. To retrieve calendar IDs call the calendarList.list method. If you want to access the primary calendar of the c
`send_updates`	string	—	Guests who should receive notifications about the change of the event's organizer. Acceptable values are: "all": Notifications are sent to all guests. "external

Parameters from the server's own tool schema.

RISK

Why GOOGLESUPER_EVENTS_MOVE is rated Medium

Moving an event to another calendar and changing its organizer constitutes modification of data (the event's properties and permissions), but the action is reversible—an organizer can move an event back or restore the original organizer. This fits the Write category rather than Execute or Destructive.

From the tool's definition Tool description states it 'Moves an event to another calendar' and 'changes an event's organizer.' This modifies the ownership and calendar association of an event, which is a reversible change to event metadata.

Risk signalsAccepts file system path (destination)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs GOOGLESUPER_EVENTS_MOVE safely

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

GOOGLESUPER_EVENTS_MOVE Rate-limited

GOOGLESUPER_EVENTS_MOVE 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": {
    "GOOGLESUPER_EVENTS_MOVE": {
      "limits": [
        {
          "counter": "googlesuper_events_move_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 Google Super, apply this rule, and every GOOGLESUPER_EVENTS_MOVE call is checked against it from then on.

FAQ

Questions about GOOGLESUPER_EVENTS_MOVE

What does the GOOGLESUPER_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 Super MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does GOOGLESUPER_EVENTS_MOVE accept? +

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

How do I enforce a policy on GOOGLESUPER_EVENTS_MOVE? +

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

What risk level is GOOGLESUPER_EVENTS_MOVE? +

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

Can I rate-limit GOOGLESUPER_EVENTS_MOVE? +

Yes. Add a rate_limit block to the GOOGLESUPER_EVENTS_MOVE 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 GOOGLESUPER_EVENTS_MOVE completely? +

Set action: deny in the PolicyLayer policy for GOOGLESUPER_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 GOOGLESUPER_EVENTS_MOVE? +

GOOGLESUPER_EVENTS_MOVE is provided by the Google Super MCP server (googlesuper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Google Super, and thousands of servers like it.

This server

All 200 Google Super tools →

Across the catalogue

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

Guides

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