Get real-time arrival information for trains at a specific station, including platform numbers, delays, origin stations, and any relevant travel notes. Returns a list of upcoming arrivals with timing, origin, and status information.
AI agents call get_arrivals to retrieve information from NS Travel Information MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries real-time train arrival data from NS (Dutch Railways). It performs a read-only operation that fetches existing information about train schedules and status without creating, modifying, deleting, or executing any actions.
From the tool's definition Tool description states 'Get real-time arrival information' and 'Returns a list of upcoming arrivals with timing, origin, and status information.' The verb 'Get' and the nature of returning information indicates data retrieval with no side effects.
Documented attack patterns abuse exactly the kind of access get_arrivals gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and NS Travel Information MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_arrivals:
{
"version": "1",
"default": "deny",
"tools": {
"get_arrivals": {}
}
}get_arrivals is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get real-time arrival information for trains at a specific station, including platform numbers, delays, origin stations, and any relevant travel notes. Returns a list of upcoming arrivals with timing, origin, and status information. It is categorised as a Read tool in the NS Travel Information MCP Server MCP Server, which means it retrieves data without modifying state.
Register the NS Travel Information MCP Server MCP server in PolicyLayer and add a rule for get_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 NS Travel Information MCP Server. Nothing to install.
get_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 get_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 get_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.
get_arrivals is provided by the NS Travel Information MCP Server MCP server (r-huijts/ns-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 NS Travel Information MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
8 NS Travel Information MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.