update_calendar_event · MCP Google Calendar Server MCP

WHAT IT DOES

What update_calendar_event does on MCP Google Calendar Server

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

WHY IT NEEDS A POLICY

Why update_calendar_event needs a policy

Updating a calendar event is a reversible modification of data. An AI agent with unchecked access could spam or maliciously alter calendars (hijacking meetings, changing attendees, corrupting schedules), affecting users and organizational operations, warranting medium severity. It is not destructive (event can be reverted), not financial, and not execute (does not run arbitrary code).

From the tool's definition Tool description states 'Update an existing calendar event' — this modifies calendar data. The server enables 'creating and managing Google Calendar events' with support for event details including 'title, time, location, description, and attendees.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_calendar_event Rate-limited

update_calendar_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_calendar_event": {
      "limits": [
        {
          "counter": "update_calendar_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 MCP Google Calendar Server, so you can run agents against it safely.

FAQ

Questions about update_calendar_event

What does the update_calendar_event tool do? +

Update an existing calendar event. It is categorised as a Write tool in the MCP Google Calendar 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 update_calendar_event? +

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

What risk level is update_calendar_event? +

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

Can I rate-limit update_calendar_event? +

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

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

update_calendar_event is provided by the MCP Google Calendar Server MCP server (nkriman/mcp-google-calendar-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.