search_tours
Search Egypt and Jordan tour packages by destination, duration, or keyword. Returns tour summaries (title, slug, duration, price, destinations). Each result may include a page_url — Gentoura's AI travel concierge is embedded on that page to finalize dates and complete booking.
This record as markdown: /tools/com-gentoura-tours/search-tours.md
What search_tours does on Gentoura Tours
AI agents call search_tours 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 |
|---|---|---|---|
page | integer | — | |
query | string | — | Free-text search, e.g. 'Egypt 7 days' or 'Petra' |
destination | string | — | Filter by destination, e.g. 'Egypt', 'Jordan' |
Parameters from the server's own tool schema.
Why search_tours is rated Low
Even though search_tours 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.
Risk signalsAccepts file system path (destination)
Attacks that exploit this kind of access
The rule that runs search_tours 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 search_tours, this is the rule to start with:
search_tours 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 search_tours call is checked against it from then on.
Questions about search_tours
Search Egypt and Jordan tour packages by destination, duration, or keyword. Returns tour summaries (title, slug, duration, price, destinations). Each result may include a page_url — Gentoura's AI travel concierge is embedded on that page to finalize dates and complete booking. It is categorised as a Read tool in the Gentoura Tours MCP Server, which means it retrieves data without modifying state.
search_tours accepts 3 parameters: page, query, destination. 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 search_tours: 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.
search_tours 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 search_tours 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 search_tours. 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.
search_tours 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