[tourradar] Use this when the user describes what they want in natural language and you need AI-powered semantic search to understand their intent. Before use this tool, please READ all possible filters. PLESE USE FILTERS, when can be used, to make search faster and much more precise. Please use ...
Risk signalsHigh parameter count (40 properties)
Part of the MolTravel server.
Free to start. No card required.
AI agents call tourradar_vertex-tour-search to retrieve information from MolTravel without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though tourradar_vertex-tour-search only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"tourradar_vertex-tour-search": {}
}
}See the full MolTravel policy for all 57 tools.
These attack patterns abuse exactly the kind of access tourradar_vertex-tour-search gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
[tourradar] Use this when the user describes what they want in natural language and you need AI-powered semantic search to understand their intent. Before use this tool, please READ all possible filters. PLESE USE FILTERS, when can be used, to make search faster and much more precise. Please use start_city, end_city, cities, countries, start_country, end_country filters if possible. You can use multiple of them. AI-powered semantic search for tours using natural language queries combined with optional filters. Uses Google Vertex AI to understand intent and find relevant tours based on descriptions, themes, or specific requests. Use vertex-tour-search when: - The user describes what they want in natural language - You need semantic/AI-powered search to understand intent - Combining natural language with filters for refined results Examples: - "Family-friendly safari with kids under 12" - "Romantic honeymoon trip with beach and mountains" - "Adventure tour with hiking and camping for beginners" - "Cultural immersion experience with local homestays" - "Wine tasting tour through European countryside" Input Required - textSearch: Natural language description of what the user is looking for - display_mode: How to display results — "listing" (default, carousel of tour cards) or "map" (interactive map view) Optional Filters Location Filters | Filter | Type | Description | | --------------- | -------- | -------------------------------------------------------------------------- | | start_country | string[] | Country where tour BEGINS (ISO 3166-1 alpha-2 codes). OR logic. | | end_country | string[] | Country where tour ENDS (ISO 3166-1 alpha-2 codes). OR logic. | | start_city | number[] | City IDs where tour starts. Use b2b-cities-search to find IDs. OR logic. | | end_city | number[] | City IDs where tour ends. Use b2b-cities-search to find IDs. OR logic. | | countries | object | Countries visited DURING the itinerary. Supports AND/OR operator. | | cities | object | Cities visited on the itinerary. Supports AND/OR operator. | Range Filters | Filter | Type | Description | | ---------------- | ------------------------ | ------------------------------------------------------------------------------------ | | duration | { min, max } | Tour length in days | | max_group_size | { min, max } | Maximum group size range | | min_group_size | { min, max } | Minimum group size range | | min_age | { min, max } | Minimum age requirement range. E.g., { min: 1, max: 12 } finds family-friendly tours | | max_age | { min, max } | Maximum age limit range. E.g., { min: 18, max: 39 } finds youth-specific tours | | price | { min, max, currency } | Price range (currency: "EUR") | AND/OR Filters These filters support both AND and OR operators: | Filter | Values | Description | | ------------ | ------------------------ | ---------------------------------- | | departures | YYYY-MM strings | Filter by departure months | | countries | ISO 3166-1 alpha-2 codes | Countries visited during itinerary | | cities | City IDs | Cities visited on itinerary | Structure: { values: [...], operator: "AND" | "OR" } - OR (default): Tour matches ANY of the specified values - AND: Tour must match ALL specified values Examples Simple text search json { "textSearch": "family adventure with wildlife" } With location filters json { "textSearch": "hiking adventure", "start_country": ["DE", "AT"], "countries": { "values": ["IT", "CH"], "operator": "AND" } } With range filters json { "textSearch": "luxury beach vacation", "duration": { "min": 7, "max": 14 }, "price": { "min": 2000, "max": 5000, "currency": "EUR" }, "max_group_size": { "min": 1, "max": 16 } } With age filters json { "textSearch": "family safari with young children", "min_age": { "min": 1, "max": 6 }, "duration": { "min": 7, "max": 14 } } With departure dates json { "textSearch": "northern lights tour", "departures": { "values": ["2026-01", "2026-02", "2026-03"], "operator": "OR" } } Map display mode json { "textSearch": "hiking tours in the Alps", "display_mode": "map", "countries": { "values": ["AT", "CH"], "operator": "OR" } } Response Returns a list of tours matching the query, each containing: - Tour ID, name, and URL - Operator information - Brief description matching the query context. It is categorised as a Read tool in the MolTravel MCP Server, which means it retrieves data without modifying state.
Register the MolTravel MCP server in PolicyLayer and add a rule for tourradar_vertex-tour-search: 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 MolTravel. Nothing to install.
tourradar_vertex-tour-search 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 tourradar_vertex-tour-search 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 tourradar_vertex-tour-search. 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.
tourradar_vertex-tour-search is provided by the MolTravel MCP server (https://mcp.moltravel.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 57 MolTravel tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.