irctc.trains.search
Search trains running between two Indian railway stations. Returns train number, name, departure/arrival time, distance, class availability (1A/2A/3A/SL/CC/EC), and running days (Mon-Sun).
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/irctc.trains.search.md
What irctc.trains.search does on Apibase
AI agents call irctc.trains.search to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
date_of_journey | string | Yes | Journey date in YYYY-MM-DD format. Must be within the next 120 days from today. Example: 2026-05-15. |
to_station_code | string | Yes | Destination station code (3-5 uppercase letters, same format as from_station_code). Use irctc.station_search to discover codes by name. |
from_station_code | string | Yes | Origin station code (3-5 uppercase letters). Examples: NDLS (New Delhi), CSMT (Mumbai CST), HWH (Howrah Kolkata), MAS (Chennai Central), SBC (Bengaluru). |
Parameters from the server's own tool schema.
Why irctc.trains.search is rated Low
Tool retrieves public railway schedule data without side effects or modifications.
From the tool's definition Search trains, returns train number, name, times, distance, availability.
Attacks that exploit this kind of access
The rule that runs irctc.trains.search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For irctc.trains.search, this is the rule to start with:
irctc.trains.search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every irctc.trains.search call is checked against it from then on.
Questions about irctc.trains.search
Search trains running between two Indian railway stations. Returns train number, name, departure/arrival time, distance, class availability (1A/2A/3A/SL/CC/EC), and running days (Mon-Sun). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
irctc.trains.search accepts 3 parameters: date_of_journey, to_station_code, from_station_code. Required: date_of_journey, to_station_code, from_station_code. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for irctc.trains.search: 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 Apibase. Nothing to install.
irctc.trains.search 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 irctc.trains.search 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 irctc.trains.search. 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.
irctc.trains.search is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue