transport-rest.transit.plan_journey

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 52 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/transport-rest.transit.plan-journey.md

WHAT IT DOES

What transport-rest.transit.plan_journey does on Apibase

AI agents call transport-rest.transit.plan_journey to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`arrival`	string	—	ISO 8601 date-time to arrive at or before. Mutually exclusive with departure.
`results`	integer	—	Maximum number of journey options to return (default 3, max 10).
`departure`	string	—	ISO 8601 date-time to depart at or after (e.g. "2026-09-01T08:00:00+02:00"). Mutually exclusive with arrival; defaults to now if neither is set.
`to_stop_id`	string	Yes	Destination stop/station ID, obtained from transport-rest.location_search or transport-rest.nearby_stops.
`from_stop_id`	string	Yes	Origin stop/station ID, obtained from transport-rest.location_search or transport-rest.nearby_stops.

Parameters from the server's own tool schema.

RISK

Why transport-rest.transit.plan_journey is rated Low

Retrieves transit routing information without modifying data or executing external operations.

From the tool's definition plan journey between stops, leg-by-leg routing, real-time delays, duration

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs transport-rest.transit.plan_journey safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For transport-rest.transit.plan_journey, this is the rule to start with:

transport-rest.transit.plan_journey Allowed

transport-rest.transit.plan_journey is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "transport-rest.transit.plan_journey": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every transport-rest.transit.plan_journey call is checked against it from then on.

FAQ

Questions about transport-rest.transit.plan_journey

What does the transport-rest.transit.plan_journey tool do? +

Plan a public transit journey between two Berlin/Brandenburg stops, with leg-by-leg routing (lines, transfers, real-time delays, duration). Stop IDs come from transport-rest.transit.search_locations or transport-rest.transit.nearby_stops. Data: v6.bvg.transport.rest (community HAFAS wrapper for BVG), no auth required, 100 req/min. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does transport-rest.transit.plan_journey accept? +

transport-rest.transit.plan_journey accepts 5 parameters: arrival, results, departure, to_stop_id, from_stop_id. Required: to_stop_id, from_stop_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on transport-rest.transit.plan_journey? +

Register the Apibase MCP server in PolicyLayer and add a rule for transport-rest.transit.plan_journey: 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 Apibase. Nothing to install.

What risk level is transport-rest.transit.plan_journey? +

transport-rest.transit.plan_journey is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit transport-rest.transit.plan_journey? +

Yes. Add a rate_limit block to the transport-rest.transit.plan_journey 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 transport-rest.transit.plan_journey completely? +

Set action: deny in the PolicyLayer policy for transport-rest.transit.plan_journey. 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 transport-rest.transit.plan_journey? +

transport-rest.transit.plan_journey is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →