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

WHAT IT DOES

What update-event does on Google Calendar MCP Server

AI agents use update-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 update-event needs a policy

This tool modifies existing calendar event data reversibly. While it changes user data, the change is not destructive (the event is not deleted) and can be undone by updating again.

From the tool's definition Tool name 'update-event' and description 'Update an existing calendar event' indicate modification of existing data. The server description confirms support for 'editing' calendar events.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

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 update-event

What does the update-event tool do? +

Update an existing calendar event. 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 update-event? +

Register the Google Calendar MCP Server 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 Google Calendar MCP Server. 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 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.

// THE FULL RECORD

update-event is one line of Google Calendar MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →