Create a complete trip skeleton with stops, activities grouped by day, transport legs, and budget estimates. Accepts multiple destinations, date range, travel vibes, persona, budget tier, and group type. Returns a ready-to-use trip plan with curated city-specific activities (50 cities), weather-a...
Risk signalsHigh parameter count (10 properties)
Part of the Pulse server.
Free to start. No card required.
AI agents use create_trip_skeleton 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 create_trip_skeleton 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": {
"create_trip_skeleton": {
"limits": [
{
"counter": "create_trip_skeleton_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 create_trip_skeleton 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.
Create a complete trip skeleton with stops, activities grouped by day, transport legs, and budget estimates. Accepts multiple destinations, date range, travel vibes, persona, budget tier, and group type. Returns a ready-to-use trip plan with curated city-specific activities (50 cities), weather-aware scheduling, and realistic cost estimates in EUR.. 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 create_trip_skeleton: 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.
create_trip_skeleton 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 create_trip_skeleton 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 create_trip_skeleton. 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.
create_trip_skeleton 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.