irail.transit.vehicle
Get the complete stop schedule for a specific Belgian train — returns all stations the train calls at with scheduled times, actual delays, platform numbers, occupancy levels, and whether the train has already departed each stop. Train IDs are returned by the liveboard and connections tools. No au...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/irail.transit.vehicle.md
What irail.transit.vehicle does on Apibase
AI agents call irail.transit.vehicle 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 |
|---|---|---|---|
id | string | Yes | Vehicle/train ID in iRail format (e.g. "BE.NMBS.IC1810", "BE.NMBS.S22308"). Obtain from liveboard or connections response. |
date | string | — | Date in DDMMYY format (e.g. "290626" for 29 June 2026). Defaults to today. |
lang | string | — | Language for station names. Default: en. |
Parameters from the server's own tool schema.
Why irail.transit.vehicle is rated Low
Tool retrieves transit schedule data without modification, deletion, or execution capabilities.
From the tool's definition Get complete stop schedule, returns stations with times, delays, platform numbers, occupancy levels
Attacks that exploit this kind of access
The rule that runs irail.transit.vehicle 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.vehicle, this is the rule to start with:
irail.transit.vehicle 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.vehicle call is checked against it from then on.
Questions about irail.transit.vehicle
Get the complete stop schedule for a specific Belgian train — returns all stations the train calls at with scheduled times, actual delays, platform numbers, occupancy levels, and whether the train has already departed each stop. Train IDs are returned by the liveboard and connections tools. No auth required. Data: iRail SNCB/NMBS Belgium. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
irail.transit.vehicle accepts 3 parameters: id, date, lang. Required: id. 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.vehicle: 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.vehicle 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.vehicle 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.vehicle. 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.vehicle 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