Get realtime timetable for a train, including actual vs scheduled times. Requires authentication in config.
AI agents call tool_get_realtime_timetable 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.
The tool queries and returns timetable information without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that retrieves existing data from the Koleo API. The authentication requirement does not change the nature of the operation—it remains a retrieval function.
From the tool's definition Tool retrieves 'realtime timetable for a train, including actual vs scheduled times' with no modification, deletion, or execution of commands. This is a data retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access tool_get_realtime_timetable gives an agent:
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_realtime_timetable:
{
"version": "1",
"default": "deny",
"tools": {
"tool_get_realtime_timetable": {}
}
} tool_get_realtime_timetable is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get realtime timetable for a train, including actual vs scheduled times. Requires authentication in config. It is categorised as a Read tool in the Koleo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Koleo MCP Server MCP server in PolicyLayer and add a rule for tool_get_realtime_timetable: 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.
tool_get_realtime_timetable 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 tool_get_realtime_timetable 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 tool_get_realtime_timetable. 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.
tool_get_realtime_timetable 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.
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.