journey_with_layover
AI agents call journey_with_layover to retrieve information from Swiss Rail without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to query train journey data with layover information, consistent with sibling tools that retrieve connections and station information. The server is described as enabling users to 'query' and 'plan journeys using natural language,' indicating read-only operations. No side effects, modifications, or destructive actions are implied.
From the tool's definition Tool name 'journey_with_layover' and sibling tools (get_connections, get_stationboard, accessible_route, bike_friendly_route) are all read-only query operations for retrieving public transport information.
Attacks that exploit this kind of access
journey_with_layover. It is categorised as a Read tool in the Swiss Rail MCP Server, which means it retrieves data without modifying state.
Register the Swiss Rail MCP server in PolicyLayer and add a rule for journey_with_layover: 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 Swiss Rail. Nothing to install.
journey_with_layover 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 journey_with_layover 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 journey_with_layover. 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.
journey_with_layover is provided by the Swiss Rail MCP server (kintscher/swiss-rail-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →