rail_historical_station_counts
Return LTA’s published historical station-count series. Coverage is 2004–2017 and excludes 2015–2016 records.
This record as markdown: /tools/olano-mcp-singapore/rail-historical-station-counts.md
What rail_historical_station_counts does on Mcp Singapore
AI agents call rail_historical_station_counts 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 |
|---|---|---|---|
toYear | integer | — | |
fromYear | integer | — |
Parameters from the server's own tool schema.
Why rail_historical_station_counts is rated Low
Even though rail_historical_station_counts 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_historical_station_counts 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_historical_station_counts, this is the rule to start with:
rail_historical_station_counts 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_historical_station_counts call is checked against it from then on.
Questions about rail_historical_station_counts
Return LTA’s published historical station-count series. Coverage is 2004–2017 and excludes 2015–2016 records. It is categorised as a Read tool in the Mcp Singapore MCP Server, which means it retrieves data without modifying state.
rail_historical_station_counts accepts 2 parameters: toYear, fromYear. 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_historical_station_counts: 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_historical_station_counts 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_historical_station_counts 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_historical_station_counts. 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_historical_station_counts 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