insert_calendar · Google Calendar MCP Server MCP

WHAT IT DOES

What insert_calendar does on Google Calendar MCP Server

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

This tool creates a new calendar resource, which is a reversible write operation. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), involve financial transactions (would be Financial), or merely read data (would be Read).

From the tool's definition Tool name 'insert_calendar' and description 'Creates a secondary calendar' indicate data creation. The verb 'insert' and 'creates' are explicit indicators of write operations that modify the calendar structure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

insert_calendar Rate-limited

insert_calendar 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": {
      "limits": [
        {
          "counter": "insert_calendar_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

What does the insert_calendar tool do? +

Creates a secondary calendar. 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? +

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

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

Can I rate-limit insert_calendar? +

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

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

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