quick_add_event · Google Calendar MCP Server MCP

WHAT IT DOES

What quick_add_event does on Google Calendar MCP Server

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

This tool creates new calendar events, which is a Write operation—it modifies data (adds events to the calendar) but the action is reversible (events can be deleted). The severity is medium because misuse could result in calendar pollution or scheduling conflicts, but the impact is limited to calendar data and can be undone.

From the tool's definition Tool description states it "Creates an event" which is a write operation that modifies calendar data. The tool name "quick_add_event" and description confirm it performs event creation, a reversible data modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

quick_add_event Rate-limited

quick_add_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": {
    "quick_add_event": {
      "limits": [
        {
          "counter": "quick_add_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 quick_add_event

What does the quick_add_event tool do? +

Creates an event based on a simple text string. 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 quick_add_event? +

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

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

Can I rate-limit quick_add_event? +

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

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

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