create_event

A write tool on the Calendar MCP server.

SERVERCalendar SOURCEdeciduus/calendar-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/deciduus-calendar-mcp/create-event.md

WHAT IT DOES

What create_event does on Calendar

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

RISK

Why create_event is rated Medium

Creating calendar events modifies data (adds new calendar entries) but does so reversibly—events can be deleted or modified later. This is a Write operation. Severity is medium because misuse could disrupt schedules, create false meetings, or cause organizational confusion, but lacks financial or irreversible consequences.

From the tool's definition Tool name 'create_event' indicates creation of calendar events. Sibling tools include 'delete_event' and 'add_attendee', establishing this as a calendar management server where create_event creates new calendar entries.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_event safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Calendar, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_event, this is the rule to start with:

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.

The button opens the PolicyLayer dashboard: create your workspace, connect Calendar, apply this rule, and every create_event call is checked against it from then on.

FAQ

Questions about create_event

What does the create_event tool do? +

create_event is a write tool on the Calendar MCP server. It is categorised as a Write tool in the Calendar 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 Calendar 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 Calendar. 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 Calendar MCP server (deciduus/calendar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Calendar, and thousands of servers like it.

This server

All 12 Calendar tools →

Across the catalogue

calendar_create_event on Apple Apps MCP →create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →