add_attendees_to_calendar_event

WHAT IT DOES

What add_attendees_to_calendar_event does on Wedding Planner MCP Server

AI agents use add_attendees_to_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 add_attendees_to_calendar_event needs a policy

This tool creates or modifies calendar data (attendee lists) in a reversible manner. It does not delete data, execute code, move money, or trigger external operations beyond calendar modification.

From the tool's definition Tool description states it 'Add[s] attendee email addresses to an existing Google Calendar event', which modifies calendar event data by adding new attendees. The qualifier 'without removing existing attendees' confirms the change is reversible.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_attendees_to_calendar_event Rate-limited

add_attendees_to_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": {
    "add_attendees_to_calendar_event": {
      "limits": [
        {
          "counter": "add_attendees_to_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 add_attendees_to_calendar_event

What does the add_attendees_to_calendar_event tool do? +

Add attendee email addresses to an existing Google Calendar event without removing existing attendees. 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 add_attendees_to_calendar_event? +

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

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

Can I rate-limit add_attendees_to_calendar_event? +

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

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

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