get_stationboard
AI agents call get_stationboard to retrieve information from Swiss Rail without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
A stationboard retrieves real-time or scheduled train departure/arrival information from a specific station. This is a passive data retrieval operation with no side effects, no code execution, and no data modification. The empty description lowers confidence slightly, but the sibling tools and server purpose (querying public transport) strongly indicate this is a Read operation.
From the tool's definition Tool name 'get_stationboard' and server context indicating querying of train/station data; description is empty but sibling tools (get_connections, get_disruptions, get_station_facilities) are all read-only queries.
Attacks that exploit this kind of access
get_stationboard. It is categorised as a Read tool in the Swiss Rail MCP Server, which means it retrieves data without modifying state.
Register the Swiss Rail MCP server in PolicyLayer and add a rule for get_stationboard: 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 Swiss Rail. Nothing to install.
get_stationboard 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 get_stationboard 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 get_stationboard. 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.
get_stationboard is provided by the Swiss Rail MCP server (kintscher/swiss-rail-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →