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 Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves static departure schedule and status data. It has no side effects: it neither modifies records, executes code, deletes data, nor commits financial transactions. The worst-case misuse (e.g., repeatedly querying) would cause minor resource waste, not harm to systems or users. This is a classic Read operation.
From the tool's definition Tool 'get_departures' retrieves 'real-time departure information' and 'returns a list of upcoming departures' — purely a data query with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
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 Server MCP Server, which means it retrieves data without modifying state.
Register the NS Travel Information 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 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 Server MCP server (kallivdh/ns-mcp-server). 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 →