# 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.

Agent View of the PolicyLayer registry record for `station_board_arrivals`. HTML page: https://policylayer.com/tools/dev-infranode-infranode/station-board-arrivals

## Facts

- Tool: `station_board_arrivals`
- Server: InfraNode (`https://mcp.infranode.dev/mcp`) — https://policylayer.com/tools/dev-infranode-infranode.md
- Homepage: https://github.com/street1983nk/infranode
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| 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.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "station_board_arrivals",
    "arguments": {
      "eva": "<eva>"
    }
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches InfraNode:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "station_board_arrivals": {}
  }
}
```

## Other tools on InfraNode (11)

- `air_quality` — Read — https://policylayer.com/tools/dev-infranode-infranode/air-quality.md
- `compare` — Read — https://policylayer.com/tools/dev-infranode-infranode/compare.md
- `get_city` — Read — https://policylayer.com/tools/dev-infranode-infranode/get-city.md
- `get_city_overview` — Read — https://policylayer.com/tools/dev-infranode-infranode/get-city-overview.md
- `get_city_resource` — Read — https://policylayer.com/tools/dev-infranode-infranode/get-city-resource.md
- `list_cities` — Read — https://policylayer.com/tools/dev-infranode-infranode/list-cities.md
- `pois` — Read — https://policylayer.com/tools/dev-infranode-infranode/pois.md
- `sources` — Read — https://policylayer.com/tools/dev-infranode-infranode/sources.md
- `station_board_departures` — Read — https://policylayer.com/tools/dev-infranode-infranode/station-board-departures.md
- `transit_departures` — Read — https://policylayer.com/tools/dev-infranode-infranode/transit-departures.md
- `weather` — Read — https://policylayer.com/tools/dev-infranode-infranode/weather.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=dev-infranode-infranode · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-infranode-infranode
