irail.transit.liveboard
Get real-time departures or arrivals for a Belgian railway station — returns train number, destination/origin, scheduled time, delay in minutes, platform, cancellation status, and passenger occupancy level. Defaults to departures from current time. No auth required. Data: iRail real-time SNCB/NMB...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/irail.transit.liveboard.md
What irail.transit.liveboard does on Apibase
AI agents call irail.transit.liveboard 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 |
|---|---|---|---|
date | string | — | Date in DDMMYY format (e.g. "290626" for 29 June 2026). Defaults to today. |
lang | string | — | Language for station and direction names. Default: en. |
time | string | — | Time in HHMM format (e.g. "0930" for 09:30). Defaults to current time. |
arrdep | string | — | Show arrivals or departures at the station. Default: departure. |
results | integer | — | Maximum number of trains to return. Default: 20, max: 50. |
station | string | Yes | Station name (e.g. "Gent-Sint-Pieters", "Brussel-Zuid", "Antwerpen-Centraal"). Must match the Belgian spelling. |
Parameters from the server's own tool schema.
Why irail.transit.liveboard is rated Low
Retrieves public transit schedule data with no side effects or modifications possible.
From the tool's definition Get real-time departures or arrivals, returns train number, destination, scheduled time, delay
Attacks that exploit this kind of access
The rule that runs irail.transit.liveboard 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 irail.transit.liveboard, this is the rule to start with:
irail.transit.liveboard is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every irail.transit.liveboard call is checked against it from then on.
Questions about irail.transit.liveboard
Get real-time departures or arrivals for a Belgian railway station — returns train number, destination/origin, scheduled time, delay in minutes, platform, cancellation status, and passenger occupancy level. Defaults to departures from current time. No auth required. Data: iRail real-time SNCB/NMBS Belgium train data. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
irail.transit.liveboard accepts 6 parameters: date, lang, time, arrdep, results, station. Required: station. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for irail.transit.liveboard: 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.
irail.transit.liveboard 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 irail.transit.liveboard 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 irail.transit.liveboard. 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.
irail.transit.liveboard 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.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue