rail_list_exits

List official station-exit points, optionally filtered by station name/code and exit label.

SERVERMcp Singapore SOURCE@olano/mcp-singapore

Low RISK CLASS

Category Read

Parameters 40 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/olano-mcp-singapore/rail-list-exits.md

WHAT IT DOES

What rail_list_exits does on Mcp Singapore

AI agents call rail_list_exits 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
`limit`	integer	—
`offset`	integer	—
`exitCode`	string	—
`stationQuery`	string	—

Parameters from the server's own tool schema.

RISK

Why rail_list_exits is rated Low

Even though rail_list_exits 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

RECOMMENDED RULE

The rule that runs rail_list_exits 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_exits, this is the rule to start with:

rail_list_exits Allowed

rail_list_exits is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rail_list_exits": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Singapore, apply this rule, and every rail_list_exits call is checked against it from then on.

FAQ

Questions about rail_list_exits

What does the rail_list_exits tool do? +

List official station-exit points, optionally filtered by station name/code and exit label. It is categorised as a Read tool in the Mcp Singapore MCP Server, which means it retrieves data without modifying state.

What parameters does rail_list_exits accept? +

rail_list_exits accepts 4 parameters: limit, offset, exitCode, stationQuery. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on rail_list_exits? +

Register the Mcp Singapore MCP server in PolicyLayer and add a rule for rail_list_exits: 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.

What risk level is rail_list_exits? +

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

Can I rate-limit rail_list_exits? +

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

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

rail_list_exits 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.

KEEP EXPLORING

More on Mcp Singapore, and thousands of servers like it.

This server

All 291 Mcp Singapore tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →