12 tools from the Public Transport MCP Server, categorised by risk level.
View the Public Transport policy →be_get_departures Get live departure board for a Belgian train station. be_get_vehicle Get details about a specific Belgian train vehicle by its ID. be_search_connections Search train connections in Belgium between two stations. Powered by iRail API for real-time routes and schedules. 2/5 be_search_stations Search for Belgian train stations by name. 2/5 ch_get_departures Get departure board for a Swiss train station with real-time information. ch_nearby_stations Find nearby Swiss train stations based on coordinates (latitude, longitude). ch_search_connections Search for train connections in Switzerland between two stations. Uses transport.opendata.ch API to provide real-time connection data including dep... 2/5 ch_search_stations Search for Swiss train stations by name or location. 2/5 no_nearest_stops Find nearest StopPlaces for a coordinate (lat, lon) within a radius in meters. no_search_places Autocomplete search across stops/addresses/POIs in Norway via Entur Geocoder. no_trip Door-to-door trip planning between two StopPlaces (NSR IDs). The Public Transport MCP server exposes 12 tools across 2 categories: Read, Execute.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Public Transport server.
Public Transport tools are categorised as Read (11), Execute (1). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept