Low Risk

tool_get_arrivals

Get upcoming train arrivals at a station.

How to control tool_get_arrivals ↓

What tool_get_arrivals does on Koleo MCP Server

AI agents call tool_get_arrivals to retrieve information from Koleo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why tool_get_arrivals needs a policy

This tool queries and retrieves train arrival information from the Koleo API—a passive data retrieval operation with no side effects. It matches the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The severity is low because misuse poses minimal risk; an agent could only retrieve public timetable data that is already available to users of the service.

From the tool's definition Tool name 'tool_get_arrivals' and description 'Get upcoming train arrivals at a station' indicate a retrieval operation. No modification, deletion, execution, or financial transaction occurs.

Documented attack patterns abuse exactly the kind of access tool_get_arrivals gives an agent:

How to control tool_get_arrivals

PolicyLayer is an MCP gateway — it sits between your AI agents and Koleo MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for tool_get_arrivals:

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

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

Related tools and policies

Go deeper

Questions about tool_get_arrivals

What does the tool_get_arrivals tool do? +

Get upcoming train arrivals at a station. It is categorised as a Read tool in the Koleo MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on tool_get_arrivals? +

Register the Koleo MCP Server MCP server in PolicyLayer and add a rule for tool_get_arrivals: 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 Koleo MCP Server. Nothing to install.

What risk level is tool_get_arrivals? +

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

Can I rate-limit tool_get_arrivals? +

Yes. Add a rate_limit block to the tool_get_arrivals 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 tool_get_arrivals completely? +

Set action: deny in the PolicyLayer policy for tool_get_arrivals. 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 tool_get_arrivals? +

tool_get_arrivals is provided by the Koleo MCP Server MCP server (mbratkowski/koleo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Koleo MCP Server tool call.

Start from Koleo MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

14 Koleo MCP Server tools catalogued and risk-classified — across an index of 43,000+ 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.