Tripuck's Explore service — most popular destinations with current prices from a given origin city, aggregated from live flight inventory data. Use for inspiration-style queries where the destination is unknown: "where can I fly from Istanbul?", "İstanbul'dan nereye?", "وجهات شعبية من دبي", "popu...
Part of the Tripuck server.
Free to start. No card required.
AI agents call popular_routes to retrieve information from Tripuck 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 popular_routes 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": {
"popular_routes": {}
}
}See the full Tripuck policy for all 5 tools.
These attack patterns abuse exactly the kind of access popular_routes 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.
Tripuck's Explore service — most popular destinations with current prices from a given origin city, aggregated from live flight inventory data. Use for inspiration-style queries where the destination is unknown: "where can I fly from Istanbul?", "İstanbul'dan nereye?", "وجهات شعبية من دبي", "populäre Reiseziele ab München". The LLM MUST infer the user language from the conversation and pass it via the locale parameter ("tr" Turkish, "en" English, "ar" Arabic, "az" Azerbaijani, "de" German, "ka" Georgian, "uz" Uzbek). All widget UI text and the text response are then returned in that language. If currency is not specified, a sensible default is picked from the locale (tr→TRY, en→USD, de→EUR, ar→USD, az→AZN, ka→GEL, uz→UZS).. It is categorised as a Read tool in the Tripuck MCP Server, which means it retrieves data without modifying state.
Register the Tripuck MCP server in PolicyLayer and add a rule for popular_routes: 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 Tripuck. Nothing to install.
popular_routes 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 popular_routes 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 popular_routes. 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.
popular_routes is provided by the Tripuck MCP server (tripuck894/tripuck). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 Tripuck 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.