Get detailed information about a train station
AI agents call get_station_info 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 returns static station information (details about train stations). It performs no write operations, does not execute code or external commands, does not delete data, and involves no financial transactions. The operation is read-only with no side effects, making it a Read category tool with low severity.
From the tool's definition Tool name 'get_station_info' and description 'Get detailed information about a train station' indicate a retrieval operation with no modification of data.
Attacks that exploit this kind of access
Get detailed information about a train station. 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_station_info: 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_station_info 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_station_info 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_station_info. 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_station_info 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 →