Get all guests from the Guest list sheet with their details
AI agents call get_guest_list to retrieve information from Wedding Planner MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves guest information from a Google Sheets document. It performs a query-like read operation that returns data without creating, modifying, deleting, or executing any code. The low severity reflects minimal risk; the data returned is already known to the system, and misuse would only expose information the AI already has access to.
From the tool's definition Tool name is 'get_guest_list' and description states it will 'Get all guests from the Guest list sheet with their details' — a pure retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get all guests from the Guest list sheet with their details. It is categorised as a Read tool in the Wedding Planner MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Wedding Planner MCP Server MCP server in PolicyLayer and add a rule for get_guest_list: 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.
get_guest_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_guest_list 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 get_guest_list. 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.
get_guest_list 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 →