patch_event · Google Calendar MCP Server MCP: Risk & Policy

WHAT IT DOES

What patch_event does on Google Calendar MCP Server

AI agents use patch_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 patch_event needs a policy

This tool modifies existing calendar events in a reversible manner (fields can be corrected or reverted). It does not create new events (that would be insert_event), delete events (destructive), or execute arbitrary code.

From the tool's definition Tool name 'patch_event' combined with description 'Patch fields on an existing event' indicates modification of calendar event data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

patch_event Rate-limited

patch_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": {
    "patch_event": {
      "limits": [
        {
          "counter": "patch_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 patch_event

What does the patch_event tool do? +

Patch fields on an existing 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 patch_event? +

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

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

Can I rate-limit patch_event? +

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

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

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