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 Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only information retrieval tool. It queries the NS railway database for travel routes and schedules, returning journey options without creating, modifying, deleting, or executing any operations that change system state. The tool provides real-time data to help users navigate train travel but has no capability to book tickets, modify schedules, or trigger external actions.
From the tool's definition Tool description states it 'Get[s] detailed travel routes' and 'Returns multiple route options' — purely retrieves and queries public railway schedule and journey planning data.
Attacks that exploit this kind of access
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 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_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 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 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 →