add_trip_item
Add an item (hotel, flight, activity, etc.) to a saved trip on a given day.
This record as markdown: /tools/com-getmyhotels-getmyhotels/add-trip-item.md
What add_trip_item does on GetMyHotels
AI agents use add_trip_item 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 |
|---|---|---|---|
day | integer | Yes | Day number within the trip. |
type | string | Yes | Item type. |
title | string | Yes | Item title (1-255 chars). |
sortOrder | integer | — | Order within the day (default 0). |
description | string | — | Optional notes (≤2000 chars). |
itineraryPublicId | string | Yes | The trip's public id (from `list_trips`/`save_trip`). |
Parameters from the server's own tool schema.
Why add_trip_item is rated Medium
This tool creates or modifies trip data by appending items to a user's saved trip. It is reversible (items can be removed) and has no financial implications by itself, though it operates in a booking/travel context. The moderate blast radius reflects that misconfigured additions could clutter or confuse a user's trip planning, but the operation is not destructive, not immediately financial, and not code execution.
From the tool's definition Tool description states 'Add an item...to a saved trip', which is a create/modify operation that adds data to an existing travel itinerary.
Attacks that exploit this kind of access
The rule that runs add_trip_item 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 add_trip_item, this is the rule to start with:
add_trip_item 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 add_trip_item call is checked against it from then on.
Questions about add_trip_item
Add an item (hotel, flight, activity, etc.) to a saved trip on a given day. 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.
add_trip_item accepts 6 parameters: day, type, title, sortOrder, description, itineraryPublicId. Required: day, type, title, itineraryPublicId. 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 add_trip_item: 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.
add_trip_item 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 add_trip_item 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 add_trip_item. 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.
add_trip_item 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