tripadvisor_autocomplete
Autocomplete TripAdvisor locations and places. Returns normalized TripAdvisor public typeahead candidates from the credential-free GraphQL endpoint.
This record as markdown: /tools/crawlora-mcp/tripadvisor-autocomplete.md
What tripadvisor_autocomplete does on Crawlora
AI agents call tripadvisor_autocomplete to retrieve information from Crawlora 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 |
|---|---|---|---|
q | string | Yes | Autocomplete query |
type | string | — | Optional result type hint |
limit | integer | — | Maximum results |
locale | string | — | TripAdvisor locale |
route_uid | string | — | Optional captured route uid |
scope_geo_id | integer | — | Optional scoped geo id |
typeahead_id | string | — | Optional captured typeahead id |
search_session_id | string | — | Optional captured search session id |
Parameters from the server's own tool schema.
Why tripadvisor_autocomplete is rated Low
Even though tripadvisor_autocomplete 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 tripadvisor_autocomplete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crawlora, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tripadvisor_autocomplete, this is the rule to start with:
tripadvisor_autocomplete 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 Crawlora, apply this rule, and every tripadvisor_autocomplete call is checked against it from then on.
Questions about tripadvisor_autocomplete
Autocomplete TripAdvisor locations and places. Returns normalized TripAdvisor public typeahead candidates from the credential-free GraphQL endpoint. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
tripadvisor_autocomplete accepts 8 parameters: q, type, limit, locale, route_uid, scope_geo_id, typeahead_id, search_session_id. Required: q. The full parameter table on this page comes from the server's own tool schema.
Register the Crawlora MCP server in PolicyLayer and add a rule for tripadvisor_autocomplete: 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 Crawlora. Nothing to install.
tripadvisor_autocomplete 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 tripadvisor_autocomplete 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 tripadvisor_autocomplete. 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.
tripadvisor_autocomplete is provided by the Crawlora MCP server (crawlora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crawlora, and thousands of servers like it.
This server
Across the catalogue