Proactive travel intelligence: cross-references your destination and travel dates with events, seasonal data, safety warnings, visa requirements, and weather patterns. Returns actionable alerts like "Tulip Festival in April!" or "Monsoon season — pack rain gear." Use this BEFORE or AFTER creating...
Part of the Pulse MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_trip_alerts to retrieve information from Pulse 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 get_trip_alerts 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.
tools:
get_trip_alerts:
rules:
- action: allowSee the full Pulse policy for all 29 tools.
Agents calling read-class tools like get_trip_alerts have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Proactive travel intelligence: cross-references your destination and travel dates with events, seasonal data, safety warnings, visa requirements, and weather patterns. Returns actionable alerts like "Tulip Festival in April!" or "Monsoon season — pack rain gear." Use this BEFORE or AFTER creating a trip skeleton to surface things the traveler might not know. Covers 35+ cities for events, 40+ for seasonal, 50+ for safety, 10 passports for visa.. It is categorised as a Read tool in the Pulse MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get_trip_alerts. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Pulse MCP server.
get_trip_alerts 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 get_trip_alerts rule in your Intercept 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 Intercept policy for get_trip_alerts. 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.
get_trip_alerts is provided by the Pulse MCP server (onetrip/pulse). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept