Medium Risk

save_to_planner

Create a trip plan and save it directly to the 1trip web planner. Returns a shareable URL the user can open to view, edit, and customize their trip. IMPORTANT: When presenting results to the user, do NOT show raw JSON. Instead, present a beautiful summary of the trip with cities, dates, nights, e...

Part of the Pulse MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

onetrip/pulse Write Risk 2/5

AI agents use save_to_planner 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 save_to_planner repeatedly, creating or modifying resources faster than any human could review. Intercept'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.

onetrip-pulse.yaml
tools:
  save_to_planner:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Pulse policy for all 29 tools.

Tool Name save_to_planner
Category Write
MCP Server Pulse MCP Server
Risk Level Medium

View all 29 tools →

Agents calling write-class tools like save_to_planner have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the save_to_planner tool do? +

Create a trip plan and save it directly to the 1trip web planner. Returns a shareable URL the user can open to view, edit, and customize their trip. IMPORTANT: When presenting results to the user, do NOT show raw JSON. Instead, present a beautiful summary of the trip with cities, dates, nights, estimated budget, and a clear call-to-action link to open/edit the trip in 1trip.app. Always end with the planner link.. 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.

How do I enforce a policy on save_to_planner? +

Add a rule in your Intercept YAML policy under the tools section for save_to_planner. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Pulse MCP server.

What risk level is save_to_planner? +

save_to_planner is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit save_to_planner? +

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

How do I block save_to_planner completely? +

Set action: deny in the Intercept policy for save_to_planner. 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 save_to_planner? +

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

Enforce policies on Pulse

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.