update_calendar_list_entry · Google Calendar MCP Server MCP

WHAT IT DOES

What update_calendar_list_entry does on Google Calendar MCP Server

AI agents use update_calendar_list_entry 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_calendar_list_entry needs a policy

The tool modifies calendar list entry settings (e.g., visibility, color, notification preferences) rather than creating new events or deleting calendars. While it affects user-facing calendar configuration, the operation is reversible and does not trigger external actions or financial consequences.

From the tool's definition Tool name 'update_calendar_list_entry' and description 'Updates an existing calendar on the user' indicate modification of calendar configuration/settings without deletion. This is a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_calendar_list_entry Rate-limited

update_calendar_list_entry 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_list_entry": {
      "limits": [
        {
          "counter": "update_calendar_list_entry_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_calendar_list_entry

What does the update_calendar_list_entry tool do? +

Updates an existing calendar on the user. 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_calendar_list_entry? +

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

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

Can I rate-limit update_calendar_list_entry? +

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

Set action: deny in the PolicyLayer policy for update_calendar_list_entry. 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_list_entry? +

update_calendar_list_entry 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.