Get detailed travel routes between two train stations, including transfers, real-time updates, platform information, and journey duration. Can plan trips for immediate departure or for a specific future time, with options to optimize for arrival time. Returns multiple route options with status an...
AI agents call get_travel_advice 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 queries NS railway data and returns travel advice, route options, and journey information. It has no side effects, does not execute commands, does not modify or delete data, and involves no financial transactions. It is a straightforward data retrieval operation similar to its sibling tools (get_arrivals, get_departures, get_disruptions, etc.).
From the tool's definition Tool description states it 'Get[s] detailed travel routes' and 'Returns multiple route options' — purely informational retrieval with no modification, deletion, execution, or financial impact. Verbs are all read-only: get, plan (retrieve), returns.
Documented attack patterns abuse exactly the kind of access get_travel_advice 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_travel_advice:
{
"version": "1",
"default": "deny",
"tools": {
"get_travel_advice": {}
}
}get_travel_advice 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 detailed travel routes between two train stations, including transfers, real-time updates, platform information, and journey duration. Can plan trips for immediate departure or for a specific future time, with options to optimize for arrival time. Returns multiple route options with status and crowding 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_travel_advice: 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_travel_advice 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_travel_advice 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_travel_advice. 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_travel_advice 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.