Creates a personalized travel itinerary based on user preferences
AI agents use create_itinerary to create or update resources in Server Travelplanner — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Server Travelplanner environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
budget | number | — | Budget in USD |
origin | string | Yes | Starting location |
endDate | string | Yes | End date (YYYY-MM-DD) |
startDate | string | Yes | Start date (YYYY-MM-DD) |
destination | string | Yes | Destination location |
preferences | array | — | Travel preferences |
Parameters from the server's own tool schema.
This tool creates new itinerary data, which is a reversible write operation. It modifies the user's data store by adding a new travel plan. The severity is medium because misuse could result in creation of unwanted itineraries cluttering the user's data or consuming storage resources, but the action is not destructive (can be deleted) and does not involve financial transactions or command execution.
From the tool's definition Tool name is 'create_itinerary' and description states it 'Creates a personalized travel itinerary based on user preferences'. The verb 'Creates' indicates data creation, which is a Write operation.
Risk signalsAccepts file system path (destination)
Attacks that exploit this kind of access
Creates a personalized travel itinerary based on user preferences. It is categorised as a Write tool in the Server Travelplanner MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_itinerary accepts 6 parameters: budget, origin, endDate, startDate, destination, preferences. Required: origin, endDate, startDate, destination. The full parameter table on this page comes from the server's own tool schema.
Register the Server Travelplanner MCP server in PolicyLayer and add a rule for create_itinerary: 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 Server Travelplanner. Nothing to install.
create_itinerary 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 create_itinerary 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 create_itinerary. 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.
create_itinerary is provided by the Server Travelplanner MCP server (@gongrzhe/server-travelplanner-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 →