calendar-update-event · Google Services MCP Server MCP

WHAT IT DOES

What calendar-update-event does on Google Services MCP Server

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

WHY IT NEEDS A POLICY

Why calendar-update-event needs a policy

This tool modifies calendar event data (time, title, description, attendees, etc.) but does not delete or destroy data. Updates are reversible—a user can modify an event back to its previous state or correct mistakes. While calendar data can be sensitive (revealing schedules, meeting details, attendee information), the impact is limited to data modification within the user's calendar system.

From the tool's definition Tool name 'calendar-update-event' and description 'Update an existing calendar event' indicate modification of existing data in a reversible manner.

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 Services MCP Server, so you can run agents against it safely.

FAQ

Questions about calendar-update-event

What does the calendar-update-event tool do? +

Update an existing calendar event. It is categorised as a Write tool in the Google Services 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 Services 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 Services 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 Services MCP Server MCP server (ricleedo/google-service-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.