get-station-code-of-citys
通过中文城市名查询代表该城市的 station_code。此接口主要用于在用户提供城市名作为出发地或到达地时，为接口准备 station_code 参数。
This record as markdown: /tools/deniselewis200081-rail/get-station-code-of-citys.md
What get-station-code-of-citys does on 12306 Ticket Search Server
AI agents call get-station-code-of-citys 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 |
|---|---|---|---|
citys | string | — | 要查询的城市，比如"北京"。若要查询多个城市，请用|分割，比如"北京|上海"。 |
Parameters from the server's own tool schema.
Why get-station-code-of-citys is rated Low
This tool performs a simple data retrieval operation - it queries a database to return station codes corresponding to city names provided by users. This is a read-only operation with no side effects, reversible actions, code execution, data destruction, or financial impact. It serves as a prerequisite lookup for other ticket search operations.
From the tool's definition Tool name 'get-station-code-of-citys' and description 'query station_code by Chinese city name' indicate a lookup/query operation that retrieves station codes for user-provided city names.
Attacks that exploit this kind of access
The rule that runs get-station-code-of-citys 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-code-of-citys, this is the rule to start with:
get-station-code-of-citys 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-code-of-citys call is checked against it from then on.
Questions about get-station-code-of-citys
通过中文城市名查询代表该城市的 station_code。此接口主要用于在用户提供城市名作为出发地或到达地时，为接口准备 station_code 参数。. 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-code-of-citys accepts 1 parameter: citys. 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-code-of-citys: 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-code-of-citys 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-code-of-citys 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-code-of-citys. 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-code-of-citys 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