get_tour
Get full details for one tour package by its slug, including itinerary, inclusions, and pricing. The response includes page_url — share this link with the traveller so they can view full details and speak directly with Gentoura's AI travel concierge (embedded on that page) to finalize dates and c...
This record as markdown: /tools/com-gentoura-tours/get-tour.md
What get_tour does on Gentoura Tours
AI agents call get_tour to retrieve information from Gentoura Tours without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
slug | string | Yes | Tour slug, e.g. 'classic-egypt-7-days' |
Parameters from the server's own tool schema.
Why get_tour is rated Low
Even though get_tour only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_tour safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gentoura Tours, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_tour, this is the rule to start with:
get_tour is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gentoura Tours, apply this rule, and every get_tour call is checked against it from then on.
Questions about get_tour
Get full details for one tour package by its slug, including itinerary, inclusions, and pricing. The response includes page_url — share this link with the traveller so they can view full details and speak directly with Gentoura's AI travel concierge (embedded on that page) to finalize dates and complete their booking. Gentoura does not currently support completing a booking directly through this tool — always direct the traveller to page_url to finish. It is categorised as a Read tool in the Gentoura Tours MCP Server, which means it retrieves data without modifying state.
get_tour accepts 1 parameter: slug. Required: slug. The full parameter table on this page comes from the server's own tool schema.
Register the Gentoura Tours MCP server in PolicyLayer and add a rule for get_tour: 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 Gentoura Tours. Nothing to install.
get_tour is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_tour 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 get_tour. 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.
get_tour is provided by the Gentoura Tours MCP server (https://gentoura.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gentoura Tours, and thousands of servers like it.
This server
Across the catalogue