create_calendar_event · Wedding Planner MCP Server MCP

WHAT IT DOES

What create_calendar_event does on Wedding Planner MCP Server

AI agents use create_calendar_event to create or update resources in Wedding Planner MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wedding Planner MCP Server environment.

WHY IT NEEDS A POLICY

Why create_calendar_event needs a policy

Creating a calendar event is a reversible write operation that creates new data in Google Calendar. It modifies the user's calendar by adding an event, but this action can be undone by deleting the event. The severity is medium because misuse could create numerous spurious events cluttering the calendar, but the impact is contained to a single user's calendar and the action is fully reversible.

From the tool's definition The tool 'create_calendar_event' creates a new Google Calendar event. The description explicitly states 'Create a Google Calendar event', which is a write operation that adds data to the user's calendar.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_calendar_event Rate-limited

create_calendar_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_calendar_event": {
      "limits": [
        {
          "counter": "create_calendar_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 Wedding Planner MCP Server, so you can run agents against it safely.

FAQ

Questions about create_calendar_event

What does the create_calendar_event tool do? +

Create a Google Calendar event. Use YYYY-MM-DD for all-day events or RFC3339 date-time for timed events. It is categorised as a Write tool in the Wedding Planner 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_calendar_event? +

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

What risk level is create_calendar_event? +

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

Can I rate-limit create_calendar_event? +

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

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

create_calendar_event is provided by the Wedding Planner MCP Server MCP server (kiboud/weddingplanner_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.