Get comprehensive information about current and planned disruptions on the Dutch railway network. Returns details about maintenance work, unexpected disruptions, alternative transport options, impact on travel times, and relevant advice. Can filter for active disruptions and specific disruption t...
AI agents call get_disruptions 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 data retrieval tool that queries the NS railway network status and returns informational data to users. It has no side effects, does not modify or delete data, does not execute external operations, and involves no financial transactions. The capability to filter results is a standard read operation.
From the tool's definition The tool 'get_disruptions' retrieves information about railway disruptions, maintenance work, and alternative transport options. The description uses query language: 'Get comprehensive information', 'Returns details', and 'Can filter for'.
Attacks that exploit this kind of access
Get comprehensive information about current and planned disruptions on the Dutch railway network. Returns details about maintenance work, unexpected disruptions, alternative transport options, impact on travel times, and relevant advice. Can filter for active disruptions and specific disruption types. 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_disruptions: 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_disruptions 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_disruptions 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_disruptions. 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_disruptions 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 →