check_disruptions
AI agents call check_disruptions to retrieve information from NS Travel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool checks for disruptions—a query operation that retrieves status information about railway disruptions with no side effects. This is a read operation similar to its sibling tools. The empty description lowers confidence slightly, but the server context and naming pattern clearly indicate data retrieval rather than modification, deletion, or execution.
From the tool's definition Tool name 'check_disruptions' combined with server purpose of providing 'real-time Dutch Railways (NS) data for journey planning, live departures, disruptions, and station search' indicates this tool retrieves disruption information.
Attacks that exploit this kind of access
check_disruptions. It is categorised as a Read tool in the NS Travel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the NS Travel MCP Server MCP server in PolicyLayer and add a rule for check_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 MCP Server. Nothing to install.
check_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 check_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 check_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.
check_disruptions is provided by the NS Travel MCP Server MCP server (lauragift21/ns-travel-mcp). 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 →