create_detailed_calendar_event

WHAT IT DOES

What create_detailed_calendar_event does on Wedding Planner MCP Server

AI agents use create_detailed_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_detailed_calendar_event needs a policy

This tool creates new calendar events in Google Calendar, which is a reversible write operation. While it modifies the calendar state and can invite attendees (introducing side effects like notifications), the action itself can be undone by deleting the event.

From the tool's definition Tool description states it 'Create[s] a Google Calendar event' with configurable details including 'attendees, recurrence, reminders, visibility, color, and guest permissions.' The word 'Create' indicates a write operation that generates a new calendar entry.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_detailed_calendar_event Rate-limited

create_detailed_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_detailed_calendar_event": {
      "limits": [
        {
          "counter": "create_detailed_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_detailed_calendar_event

What does the create_detailed_calendar_event tool do? +

Create a Google Calendar event with optional details such as description, location, attendees, recurrence, reminders, visibility, color, and guest permissions. 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_detailed_calendar_event? +

Register the Wedding Planner MCP Server MCP server in PolicyLayer and add a rule for create_detailed_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_detailed_calendar_event? +

create_detailed_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_detailed_calendar_event? +

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

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

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