station_board_arrivals
Get live arrivals for ANY railway station by its EVA number. Mirror of station_board_departures for arriving trains (all categories, real-time delays, disruption messages). Get the EVA from get_city_resource(slug, resource='stations'). Read-only.
This record as markdown: /tools/dev-infranode-infranode/station-board-arrivals.md
What station_board_arrivals does on InfraNode
AI agents call station_board_arrivals to retrieve information from InfraNode 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 |
|---|---|---|---|
eva | string | Yes | Station EVA number (digits only) from get_city_resource(slug, resource='stations'), e.g. '8000105' (Frankfurt Hbf). |
Parameters from the server's own tool schema.
Why station_board_arrivals is rated Low
This is a straightforward data retrieval tool that queries live railway station arrival information. It has no side effects, cannot modify data, and poses minimal risk if invoked by an AI agent. The read-only designation and context (part of a public open data service for German cities) confirm this is a safe Read category tool with low severity.
From the tool's definition Tool description explicitly states "Get live arrivals for ANY railway station" and "Read-only." The tool retrieves real-time train arrival data without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
The rule that runs station_board_arrivals safely
PolicyLayer is an MCP gateway: it sits between your AI agents and InfraNode, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For station_board_arrivals, this is the rule to start with:
station_board_arrivals 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 InfraNode, apply this rule, and every station_board_arrivals call is checked against it from then on.
Questions about station_board_arrivals
Get live arrivals for ANY railway station by its EVA number. Mirror of station_board_departures for arriving trains (all categories, real-time delays, disruption messages). Get the EVA from get_city_resource(slug, resource='stations'). Read-only. It is categorised as a Read tool in the InfraNode MCP Server, which means it retrieves data without modifying state.
station_board_arrivals accepts 1 parameter: eva. Required: eva. The full parameter table on this page comes from the server's own tool schema.
Register the InfraNode MCP server in PolicyLayer and add a rule for station_board_arrivals: 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 InfraNode. Nothing to install.
station_board_arrivals 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 station_board_arrivals 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 station_board_arrivals. 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.
station_board_arrivals is provided by the InfraNode MCP server (https://mcp.infranode.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on InfraNode, and thousands of servers like it.
This server
Across the catalogue