save_trip
Create a new saved trip (itinerary) for the signed-in user.
This record as markdown: /tools/com-getmyhotels-getmyhotels/save-trip.md
What save_trip does on GetMyHotels
AI agents use save_trip to create or update resources in GetMyHotels, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GetMyHotels environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
title | string | Yes | Trip title (1-255 chars). |
budget | number | — | Optional total budget. |
endDate | string | Yes | Trip end, ISO 8601 (YYYY-MM-DD). |
startDate | string | Yes | Trip start, ISO 8601 (YYYY-MM-DD). |
description | string | — | Optional notes (≤4000 chars). |
budgetCurrency | string | — | ISO 4217 currency for the budget (e.g. 'USD'). |
Parameters from the server's own tool schema.
Why save_trip is rated Medium
This tool creates and stores a new itinerary/trip resource for an authenticated user. It modifies the user's account state by adding a new record, making it a Write operation. Severity is medium because misuse could create unwanted trip records in a user's account (spam, confusion), but this is reversible and does not involve deletion, code execution, or financial transactions.
From the tool's definition Tool description states 'Create a new saved trip (itinerary) for the signed-in user.' The verb 'Create' indicates data modification, and 'saved trip' is a new resource being created in the user's account.
Attacks that exploit this kind of access
The rule that runs save_trip safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GetMyHotels, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For save_trip, this is the rule to start with:
save_trip stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GetMyHotels, apply this rule, and every save_trip call is checked against it from then on.
Questions about save_trip
Create a new saved trip (itinerary) for the signed-in user. It is categorised as a Write tool in the GetMyHotels MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
save_trip accepts 6 parameters: title, budget, endDate, startDate, description, budgetCurrency. Required: title, endDate, startDate. The full parameter table on this page comes from the server's own tool schema.
Register the GetMyHotels MCP server in PolicyLayer and add a rule for save_trip: 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 GetMyHotels. Nothing to install.
save_trip 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 save_trip 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 save_trip. 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.
save_trip is provided by the GetMyHotels MCP server (https://mcp.getmyhotels.com). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GetMyHotels, and thousands of servers like it.
This server
Across the catalogue