calendar_event_create · Google Workspace MCP: Risk & Policy

WHAT IT DOES

What calendar_event_create does on Google Workspace

AI agents use calendar_event_create to create or update resources in Google Workspace — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Workspace environment.

WHY IT NEEDS A POLICY

Why calendar_event_create needs a policy

This tool creates new data (calendar events) in Google Calendar, which is a write operation. The severity is medium because while it modifies user data and could spam/pollute a calendar if misused, it does not irreversibly destroy data (events can be deleted), does not execute arbitrary code, and does not involve financial transactions.

From the tool's definition Tool is named 'calendar_event_create' and description states 'Create an event', which creates new calendar entries. This is a reversible modification operation (events can be deleted or updated later).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

calendar_event_create Rate-limited

calendar_event_create 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": {
    "calendar_event_create": {
      "limits": [
        {
          "counter": "calendar_event_create_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 Workspace, so you can run agents against it safely.

FAQ

Questions about calendar_event_create

What does the calendar_event_create tool do? +

Create an event. start/end are RFC3339 datetimes; date-only ('2026-06-10') makes an all-day event. It is categorised as a Write tool in the Google Workspace MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on calendar_event_create? +

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

What risk level is calendar_event_create? +

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

Can I rate-limit calendar_event_create? +

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

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

calendar_event_create is provided by the Google Workspace MCP server (rajool/google-workspace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.