Add a new guest to the Guest list
AI agents use add_guest 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.
This tool creates new data (a guest entry) in a reversible manner. The operation can be undone by removing the guest, so it does not meet the Destructive threshold. It has no financial impact, does not execute code or external operations, and does not retrieve data. The blast radius is minimal—incorrect guest additions in a wedding planner affect only the guest list and can be easily corrected.
From the tool's definition Tool name 'add_guest' with description 'Add a new guest to the Guest list' indicates creation of a new record in a guest list data structure.
Attacks that exploit this kind of access
Add a new guest to the Guest list. 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.
Register the Wedding Planner MCP Server MCP server in PolicyLayer and add a rule for add_guest: 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.
add_guest is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_guest 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.
Set action: deny in the PolicyLayer policy for add_guest. 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.
add_guest 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →