Get invitations summary (counts) and vendor list
AI agents call get_invitations 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 summary information (invitation counts) and vendor lists from the wedding planner sheet. It performs a read-only query with no side effects, no data modification, and no external actions triggered. The blast radius of misuse is minimal since it only exposes aggregated metadata about invitations and vendor information already intended to be managed through the system.
From the tool's definition Tool name is 'get_invitations' and description states 'Get invitations summary (counts) and vendor list' — both indicate retrieval/query operations with no modification of data.
Attacks that exploit this kind of access
Get invitations summary (counts) and vendor list. 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_invitations: 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_invitations 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_invitations 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_invitations. 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_invitations 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 →