Low Risk

get_disruptions

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...

How to control get_disruptions ↓

AI agents call get_disruptions 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.

Low Risk

This tool queries the NS railway network's disruption data and returns informational results. It has no side effects—it does not create, modify, delete, or execute operations. The read-only nature and purely informational purpose place it squarely in the Read category with low severity, as misuse would only expose existing public transit information.

From the tool's definition Tool retrieves information about disruptions ('Get comprehensive information about current and planned disruptions'); no modification, deletion, or execution of external operations.

Documented attack patterns abuse exactly the kind of access get_disruptions 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_disruptions:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_disruptions": {}
  }
}

get_disruptions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register NS Travel Information MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_disruptions tool do? +

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 MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_disruptions? +

Register the NS Travel Information MCP 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 MCP Server. Nothing to install.

What risk level is get_disruptions? +

get_disruptions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_disruptions? +

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.

How do I block get_disruptions completely? +

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.

What MCP server provides get_disruptions? +

get_disruptions 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.

Enforce policy on every NS Travel Information MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.