create_events · Google Calendar MCP Server MCP

WHAT IT DOES

What create_events does on Google Calendar MCP Server

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

This tool creates new calendar events through the Google Calendar API, which is reversible via deletion. While creation modifies a user's calendar state and could be misused to spam events or send unwanted invitations, it does not irreversibly destroy data (Destructive), execute arbitrary code (Execute), or move money (Financial).

From the tool's definition Tool description states 'Create single, multiple, or recurring calendar events' — this creates new calendar entries. The sibling tools include 'manage_calendars' and 'update_events', establishing this as a data creation action.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_events Rate-limited

create_events 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": {
    "create_events": {
      "limits": [
        {
          "counter": "create_events_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 create_events

What does the create_events tool do? +

Create single, multiple, or recurring calendar events. 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 create_events? +

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

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

Can I rate-limit create_events? +

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

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

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