rail_list_stations
List station locations with official codes, lines, Chinese names, exit-derived coordinates, and snapshot status.
This record as markdown: /tools/olano-mcp-singapore/rail-list-stations.md
What rail_list_stations does on Mcp Singapore
AI agents call rail_list_stations to retrieve information from Mcp Singapore 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 |
|---|---|---|---|
line | string | — | |
limit | integer | — | |
offset | integer | — | |
system | string | — | |
codeSnapshotStatus | string | — |
Parameters from the server's own tool schema.
Why rail_list_stations is rated Low
Even though rail_list_stations only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs rail_list_stations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Singapore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rail_list_stations, this is the rule to start with:
rail_list_stations 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 Mcp Singapore, apply this rule, and every rail_list_stations call is checked against it from then on.
Questions about rail_list_stations
List station locations with official codes, lines, Chinese names, exit-derived coordinates, and snapshot status. It is categorised as a Read tool in the Mcp Singapore MCP Server, which means it retrieves data without modifying state.
rail_list_stations accepts 5 parameters: line, limit, offset, system, codeSnapshotStatus. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Singapore MCP server in PolicyLayer and add a rule for rail_list_stations: 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 Mcp Singapore. Nothing to install.
rail_list_stations 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_list_stations 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_list_stations. 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_list_stations is provided by the Mcp Singapore MCP server (@olano/mcp-singapore). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Singapore, and thousands of servers like it.
This server
Across the catalogue