update-event

Modify existing event. Returns: updated event with id, summary, start, end. Use when: rescheduling, changing details. Note: supports recurring event scopes (single/all/future).

SERVERMCP Google Workspace SOURCE199-mcp/mcp-google

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/199-biotechnologies-mcp-google/update-event.md

WHAT IT DOES

What update-event does on MCP Google Workspace

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

RISK

Why update-event is rated Medium

The tool modifies calendar events reversibly (not destructively). While update operations are Write category, severity is high due to: (1) ability to modify recurring events affecting potentially many calendar entries, (2) calendar data often contains time-sensitive and important commitments, (3) misuse could disrupt schedules for the account holder and attendees, (4) OAuth2 context suggests production calendar data.

From the tool's definition Tool name 'update-event' and description 'Modify existing event' explicitly indicate data modification. Description confirms 'rescheduling, changing details' use cases. Supports 'recurring event scopes' affecting multiple calendar events.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update-event safely

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

update-event Rate-limited

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

FAQ

Questions about update-event

What does the update-event tool do? +

Modify existing event. Returns: updated event with id, summary, start, end. Use when: rescheduling, changing details. Note: supports recurring event scopes (single/all/future). It is categorised as a Write tool in the MCP Google Workspace MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update-event? +

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

What risk level is update-event? +

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

Can I rate-limit update-event? +

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

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

update-event is provided by the MCP Google Workspace MCP server (199-mcp/mcp-google). 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 Workspace, and thousands of servers like it.

This server

All 26 MCP Google Workspace tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

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