Set or update the trip planning context for the current session. Use this to explicitly define or change trip parameters (destinations, dates, budget, etc.) during a multi-step conversation. Context persists across tool calls within the same session. Use action="clear" to start fresh.
Risk signalsHigh parameter count (14 properties)
Part of the Pulse server.
Free to start. No card required.
AI agents use set_trip_context to create or modify resources in Pulse. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call set_trip_context repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Pulse.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"set_trip_context": {
"limits": [
{
"counter": "set_trip_context_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Pulse policy for all 29 tools.
These attack patterns abuse exactly the kind of access set_trip_context gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Set or update the trip planning context for the current session. Use this to explicitly define or change trip parameters (destinations, dates, budget, etc.) during a multi-step conversation. Context persists across tool calls within the same session. Use action="clear" to start fresh.. It is categorised as a Write tool in the Pulse MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pulse MCP server in PolicyLayer and add a rule for set_trip_context: 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 Pulse. Nothing to install.
set_trip_context is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_trip_context 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 set_trip_context. 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.
set_trip_context is provided by the Pulse MCP server (onetrip/pulse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 Pulse 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.