Create a confirmed booking
AI agents use rezdy_agent_create_booking to create or update resources in Rezdy Agent MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rezdy Agent MCP Server environment.
This tool creates new booking records, which modifies data in the system. While it creates rather than deletes data, booking creation in a travel/payment context has significant side effects: it establishes customer commitments, reserves inventory, and may trigger financial obligations.
From the tool's definition Tool name 'rezdy_agent_create_booking' and description 'Create a confirmed booking' indicate creation of a new booking record in the travel marketplace system.
Attacks that exploit this kind of access
Create a confirmed booking. It is categorised as a Write tool in the Rezdy Agent MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rezdy Agent MCP Server MCP server in PolicyLayer and add a rule for rezdy_agent_create_booking: 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 Rezdy Agent MCP Server. Nothing to install.
rezdy_agent_create_booking 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 rezdy_agent_create_booking 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 rezdy_agent_create_booking. 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.
rezdy_agent_create_booking is provided by the Rezdy Agent MCP Server MCP server (jezweb/rezdy-agent-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 →