Get detailed information about a train station
AI agents call get_station_info 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 and retrieves static or semi-static information about train stations. It performs no modifications, deletions, code execution, or financial transactions. The operation is read-only and returns informational data. Blast radius from misuse is minimal—an attacker could only gather public travel infrastructure information.
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 side effects.
Documented attack patterns abuse exactly the kind of access get_station_info 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_station_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_station_info": {}
}
}get_station_info 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 information about a train station. 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_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 MCP 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 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.