Low Risk

cheapest_dates

Tripuck price calendar — for a given route, returns the cheapest daily price across a full month. Use this when the user shows date flexibility: "when is the cheapest day to fly IST-AYT in April?", "hangi gün daha ucuz?", "أرخص يوم للسفر", "günstigste Tage für...". Use when the user asks about ch...

Risk signalsAccepts file system path (destination)

Part of the Tripuck server.

cheapest_dates is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE TRIPUCK →

Free to start. No card required.

AI agents call cheapest_dates 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 cheapest_dates 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "cheapest_dates": {}
  }
}

See the full Tripuck policy for all 5 tools.

Get this rule live on your own Tripuck server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY TRIPUCK →

These attack patterns abuse exactly the kind of access cheapest_dates gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so cheapest_dates only ever does what you allow.

SECURE TRIPUCK →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the cheapest_dates tool do? +

Tripuck price calendar — for a given route, returns the cheapest daily price across a full month. Use this when the user shows date flexibility: "when is the cheapest day to fly IST-AYT in April?", "hangi gün daha ucuz?", "أرخص يوم للسفر", "günstigste Tage für...". Use when the user asks about cheap days, flexible travel windows, or month-level price overviews. 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.

How do I enforce a policy on cheapest_dates? +

Register the Tripuck MCP server in PolicyLayer and add a rule for cheapest_dates: 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.

What risk level is cheapest_dates? +

cheapest_dates is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit cheapest_dates? +

Yes. Add a rate_limit block to the cheapest_dates 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.

How do I block cheapest_dates completely? +

Set action: deny in the PolicyLayer policy for cheapest_dates. 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.

What MCP server provides cheapest_dates? +

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

Enforce policy on every Tripuck tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.