Get real-time departure information for trains from a specific station, including platform numbers, delays, route details, and any relevant travel notes. Returns a list of upcoming departures with timing, destination, and status information.
AI agents call get_departures 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 public transit information about train departures. It queries and returns data about schedules, platforms, and status—typical read operations. There is no capability to modify data, execute commands, delete information, or commit financial transactions. The information is read-only and informational in nature, suitable for travel planning.
From the tool's definition Tool name 'get_departures' and description states it 'Get[s] real-time departure information' and 'Returns a list of upcoming departures'. Action verbs are 'get' and 'returns', which indicate data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_departures 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_departures:
{
"version": "1",
"default": "deny",
"tools": {
"get_departures": {}
}
}get_departures 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 departure information for trains from a specific station, including platform numbers, delays, route details, and any relevant travel notes. Returns a list of upcoming departures with timing, destination, 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_departures: 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_departures 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_departures 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_departures. 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_departures 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.