calendar_update_event · Google Calendar MCP Server MCP

WHAT IT DOES

What calendar_update_event does on Google Calendar MCP Server

AI agents use calendar_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 calendar_update_event needs a policy

The tool updates calendar events, which is a reversible data modification operation. This is a Write action—it changes existing calendar data but does not permanently delete it (unlike calendar_delete_event). The description is empty, which prevents direct confirmation, but the function name and context from sibling tools provide clear evidence.

From the tool's definition Tool name 'calendar_update_event' indicates modification of calendar events. The sibling tools include 'calendar_create_event' (Write), 'calendar_delete_event' (Destructive), and 'calendar_get_event' (Read), placing this tool in the modification category.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

calendar_update_event Rate-limited

calendar_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": {
    "calendar_update_event": {
      "limits": [
        {
          "counter": "calendar_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 calendar_update_event

What does the calendar_update_event tool do? +

calendar_update_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 calendar_update_event? +

Register the Google Calendar MCP Server MCP server in PolicyLayer and add a rule for calendar_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 calendar_update_event? +

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

Can I rate-limit calendar_update_event? +

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

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

calendar_update_event is provided by the Google Calendar MCP Server MCP server (murphy360/mcp_google_calendar). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.