Fetch rail traffic information
AI agents call rail-traffic-info to retrieve information from Open Data Model Context Protocol without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves public rail traffic data without modifying, executing, deleting, or creating any resources. The context of accessing public datasets and sibling tools (endpoint-name, railway-lines, rolling-stock) further suggests informational queries only. No side effects or irreversible actions are possible.
From the tool's definition Tool name 'rail-traffic-info' and description 'Fetch rail traffic information' indicate data retrieval with no modification capabilities. The verb 'Fetch' is characteristic of read-only operations.
Attacks that exploit this kind of access
Fetch rail traffic information. It is categorised as a Read tool in the Open Data Model Context Protocol MCP Server, which means it retrieves data without modifying state.
Register the Open Data Model Context Protocol MCP server in PolicyLayer and add a rule for rail-traffic-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 Open Data Model Context Protocol. Nothing to install.
rail-traffic-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 rail-traffic-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 rail-traffic-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.
rail-traffic-info is provided by the Open Data Model Context Protocol MCP server (opendatamcp/opendatamcp). 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 →