// SCAN REPORT

Wedding Planner MCP Server

41 tools. 29 can modify or destroy data without limits.

9 destructive tools with no built-in limits. Policy required.

Last updated: 3 Jul 2026

29 can modify or destroy data

12 read-only

41 tools total

Community server · catalogue entry verified 03/07/2026

How to control Wedding Planner MCP Server ↓

TOOL MAP

What Wedding Planner MCP Server exposes to your agents

Read (12) Write / Execute (20) Destructive / Financial (9)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Wedding Planner MCP Server tools

Destructive · High delete_budget_category This tool permanently removes a budget category and all associated data from multiple locations in the wedding planner spreadsheet. Destructive · High delete_budget_item The tool performs an irreversible deletion of budget data. Destructive · High delete_calendar_event The tool performs an irreversible deletion of calendar event data. Destructive · High delete_coordination This tool permanently removes coordination items from the Google Sheets backend without apparent undo capability.

29 of Wedding Planner MCP Server's 41 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Wedding Planner MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Wedding Planner MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_budget_category": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "add_attendees_to_calendar_event": {
    "limits": [
      {
        "counter": "add_attendees_to_calendar_event_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_budget_summary": {
    "limits": [
      {
        "counter": "get_budget_summary_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Wedding Planner MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON WEDDING PLANNER →

Instant setup, no code required.

FULL CATALOGUE

All 41 Wedding Planner MCP Server tools

DESTRUCTIVE 9 tools

WRITE 20 tools

Write add_attendees_to_calendar_event Add attendee email addresses to an existing Google Calendar event without removing existing attendees. Write add_budget_category Create a new major budget category (Clones formatting and links formulas automatically) Write add_budget_item Add a new item to a specific budget category (uses smart row insertion to preserve formulas) Write add_coordination Add a new coordination role to the Coordination sheet Write add_guest Add a new guest to the Guest list Write add_invitation_vendor Add a new invitation vendor Write add_schedule Add a new schedule item to the Schedule sheet Write add_todo Add a new to-do item to the To-do sheet. Date is auto-normalized to MM/DD/YYYY — you can pass any format (e.g. Write add_vendor Add a new vendor to the Vendors sheet Write create_calendar_event Create a Google Calendar event. Use YYYY-MM-DD for all-day events or RFC3339 date-time for timed events. Write create_detailed_calendar_event Create a Google Calendar event with optional details such as description, location, attendees, recurrence, rem Write update_budget_category Rename a budget category and/or update its estimate. Detailed budget header auto-updates via formula. Write update_budget_item Update an existing budget item. Estimated cost is auto-populated from Vendors sheet via VLOOKUP. Write update_calendar_event Patch an existing Google Calendar event by event ID. Write update_coordination Update an existing coordination role by its row number Write update_guest Update a guest Write update_invitation_vendor Update an invitation vendor by row number Write update_schedule Update an existing schedule item by its row number Write update_todo Update an existing to-do item by its row number. Date is auto-normalized to MM/DD/YYYY. Write update_vendor Update a vendor by row number

READ 12 tools

Read get_budget_summary Get the budget summary categories and totals from Budget estimator Read get_calendar_event_information Get detailed information for one Google Calendar event by event ID. Read get_coordination Get all coordination roles from the Coordination sheet (columns B:H starting from row 6) Read get_detailed_budget Get all items from Detailed budget Read get_guest_list Get all guests from the Guest list sheet with their details Read get_guest_summary Get guest list statistics: total guests, attending count, response breakdown, by invitedBy Read get_invitations Get invitations summary (counts) and vendor list Read get_schedule Get all schedule items from the Schedule sheet (columns B:E starting from row 6) Read get_todos Get all to-do items from the To-do sheet (columns B:E starting from row 6) Read get_vendors Get all vendors from the Vendors sheet Read list_calendar_events List Google Calendar events ordered by start time. Defaults to upcoming events from now. Read search_guests Search guests by name, invitedBy, notes, or any field

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Wedding Planner MCP Server

Can an AI agent delete data through the Wedding Planner MCP Server MCP server? +

Yes. The Wedding Planner MCP Server server exposes 9 destructive tools including delete_budget_category, delete_budget_item, delete_calendar_event. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Wedding Planner MCP Server? +

The Wedding Planner MCP Server server has 20 write tools including add_attendees_to_calendar_event, add_budget_category, add_budget_item. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Wedding Planner MCP Server.

How many tools does the Wedding Planner MCP Server MCP server expose? +

41 tools across 3 categories: Destructive, Read, Write. 12 are read-only. 29 can modify, create, or delete data.

How do I enforce a policy on Wedding Planner MCP Server? +

Register the Wedding Planner MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Wedding Planner MCP Server tool call.

Deterministic rules across all 41 Wedding Planner MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON WEDDING PLANNER →

Instant setup, no code required.

41 Wedding Planner MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.