create-event · Google Calendar MCP Server MCP: Risk & Policy

WHAT IT DOES

What create-event does on Google Calendar MCP Server

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

Creating a calendar event is a reversible write operation. It adds data to the user's calendar but does not execute arbitrary code, delete data, or move money. The severity is medium because an AI agent misusing this could spam the user's calendar with unwanted events or create events impersonating the user, causing calendar pollution and potential social/professional disruption, though the damage is limited and…

From the tool's definition Tool name is 'create-event' and description states 'Create a new calendar event'. The server description confirms it 'Supports creating, editing, deleting, and searching calendar events'. This is a write operation that adds a new calendar entry.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create-event Rate-limited

create-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": {
    "create-event": {
      "limits": [
        {
          "counter": "create-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 Calendar MCP Server, so you can run agents against it safely.

FAQ

Questions about create-event

What does the create-event tool do? +

Create a new calendar event. 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-event? +

Register the Google Calendar MCP Server MCP server in PolicyLayer and add a rule for create-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 Calendar MCP Server. Nothing to install.

What risk level is create-event? +

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

Can I rate-limit create-event? +

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

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

create-event is provided by the Google Calendar MCP Server MCP server (progrmoiz/cal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.