Optimizes an existing itinerary based on specified criteria
AI agents use optimize_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 |
|---|---|---|---|
itineraryId | string | Yes | ID of the itinerary to optimize |
optimizationCriteria | array | Yes | Criteria for optimization (time, cost, etc.) |
Parameters from the server's own tool schema.
Optimizing an itinerary involves reading the current itinerary and writing back a modified version. This is a reversible write operation — the itinerary is updated/rearranged but not permanently destroyed. Severity is medium because a misuse could overwrite a carefully planned itinerary with an unwanted arrangement, but it is recoverable in typical systems.
From the tool's definition 'Optimizes an existing itinerary' implies modifying/updating an existing record based on specified criteria
Attacks that exploit this kind of access
Optimizes an existing itinerary based on specified criteria. 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.
optimize_itinerary accepts 2 parameters: itineraryId, optimizationCriteria. Required: itineraryId, optimizationCriteria. 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 optimize_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.
optimize_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 optimize_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 optimize_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.
optimize_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 →