# 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.

Agent View of the PolicyLayer registry record for `get_tour`. HTML page: https://policylayer.com/tools/com-gentoura-tours/get-tour

## Facts

- Tool: `get_tour`
- Server: Gentoura Tours (`https://gentoura.com/api/mcp`) — https://policylayer.com/tools/com-gentoura-tours.md
- Homepage: https://github.com/yasersamra/tripath-nextjs-360
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `slug` | string | yes | Tour slug, e.g. 'classic-egypt-7-days' |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_tour",
    "arguments": {
      "slug": "<slug>"
    }
  }
}
```

## 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.

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Gentoura Tours:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_tour": {}
  }
}
```

## Other tools on Gentoura Tours (2)

- `get_pricing` — Read — https://policylayer.com/tools/com-gentoura-tours/get-pricing.md
- `search_tours` — Read — https://policylayer.com/tools/com-gentoura-tours/search-tours.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-gentoura-tours · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-gentoura-tours