get-station-by-telecode
通过车站的 station_telecode 查询车站的详细信息，包括名称、拼音、所属城市等。此接口主要用于在已知 telecode 的情况下获取更完整的车站数据，或用于特殊查询及调试目的。一般用户对话流程中较少直接触发。
This record as markdown: /tools/deniselewis200081-rail/get-station-by-telecode.md
What get-station-by-telecode does on 12306 Ticket Search Server
AI agents call get-station-by-telecode to retrieve information from 12306 Ticket Search Server 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 |
|---|---|---|---|
stationTelecode | string | — | 车站的 `station_telecode` (3位字母编码) |
Parameters from the server's own tool schema.
Why get-station-by-telecode is rated Low
This tool retrieves and queries station information based on a telecode identifier. It performs a lookup operation that returns read-only data (station name, pinyin, city affiliation) without modifying, creating, deleting, or executing any operations.
From the tool's definition Tool description states it 'queries station detailed information' (查询车站的详细信息) by telecode, including name, pinyin, and city.
Attacks that exploit this kind of access
The rule that runs get-station-by-telecode safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 12306 Ticket Search Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get-station-by-telecode, this is the rule to start with:
get-station-by-telecode 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 12306 Ticket Search Server, apply this rule, and every get-station-by-telecode call is checked against it from then on.
Questions about get-station-by-telecode
通过车站的 station_telecode 查询车站的详细信息，包括名称、拼音、所属城市等。此接口主要用于在已知 telecode 的情况下获取更完整的车站数据，或用于特殊查询及调试目的。一般用户对话流程中较少直接触发。. It is categorised as a Read tool in the 12306 Ticket Search Server MCP Server, which means it retrieves data without modifying state.
get-station-by-telecode accepts 1 parameter: stationTelecode. The full parameter table on this page comes from the server's own tool schema.
Register the 12306 Ticket Search Server MCP server in PolicyLayer and add a rule for get-station-by-telecode: 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 12306 Ticket Search Server. Nothing to install.
get-station-by-telecode 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 get-station-by-telecode 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 get-station-by-telecode. 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.
get-station-by-telecode is provided by the 12306 Ticket Search Server MCP server (DeniseLewis200081/rail). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 12306 Ticket Search Server, and thousands of servers like it.
This server
Across the catalogue