insert_calendar_list_entry · Google Calendar MCP Server MCP

WHAT IT DOES

What insert_calendar_list_entry does on Google Calendar MCP Server

AI agents use insert_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 insert_calendar_list_entry needs a policy

This tool creates a new calendar list entry by inserting an existing calendar into the user's calendar list. This is reversible (the entry can be removed), so it falls under Write rather than Destructive. The severity is medium because while calendar metadata is not as sensitive as data deletion, unauthorized calendar additions could affect the user's calendar visibility and organization.

From the tool's definition Tool name contains 'insert' and description states 'Inserts an existing calendar into the user', indicating creation/addition of a calendar list entry. The word 'insert' is a canonical Write operation verb.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

insert_calendar_list_entry Rate-limited

insert_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": {
    "insert_calendar_list_entry": {
      "limits": [
        {
          "counter": "insert_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 insert_calendar_list_entry

What does the insert_calendar_list_entry tool do? +

Inserts an existing calendar into 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 insert_calendar_list_entry? +

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

insert_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 insert_calendar_list_entry? +

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

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

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