bike_friendly_route
AI agents call bike_friendly_route 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 or retrieve bike-friendly route data for Swiss public transport, with no indication of modification, execution, or destructive capability. The absence of a description lowers confidence slightly, but the server's stated purpose ('query train connections', 'plan journeys') and sibling tools strongly indicate this is a read-only lookup function.
From the tool's definition Tool name 'bike_friendly_route' suggests querying bike-friendly transportation information. No description provided, but sibling tools on this server (find_station, get_connections, get_disruptions, get_station_facilities, get_stationboard,…
Attacks that exploit this kind of access
bike_friendly_route. 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 bike_friendly_route: 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.
bike_friendly_route 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 bike_friendly_route 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 bike_friendly_route. 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.
bike_friendly_route 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 →