get-stations-code-in-city
通过中文城市名查询该城市 所有 火车站的名称及其对应的 station_code，结果是一个包含多个车站信息的列表。
This record as markdown: /tools/deniselewis200081-rail/get-stations-code-in-city.md
What get-stations-code-in-city does on 12306 Ticket Search Server
AI agents call get-stations-code-in-city 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 |
|---|---|---|---|
city | string | — | 中文城市名称，例如："北京", "上海" |
Parameters from the server's own tool schema.
Why get-stations-code-in-city is rated Low
This tool performs a read-only query operation that returns reference data (station codes and names) without side effects. It does not modify data, execute code, trigger external actions, or affect financial systems. The blast radius of misuse is minimal—an attacker could only obtain publicly available station information. Classification as Read is appropriate.
From the tool's definition Tool name 'get-stations-code-in-city' and description indicate it 'query[s]' (查询) and 'retrieve[s]' (retrieves) a list of station names and codes for a city. No modification, deletion, or execution of external operations is mentioned.
Attacks that exploit this kind of access
The rule that runs get-stations-code-in-city 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-stations-code-in-city, this is the rule to start with:
get-stations-code-in-city 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-stations-code-in-city call is checked against it from then on.
Questions about get-stations-code-in-city
通过中文城市名查询该城市 所有 火车站的名称及其对应的 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-stations-code-in-city accepts 1 parameter: city. 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-stations-code-in-city: 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-stations-code-in-city 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-stations-code-in-city 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-stations-code-in-city. 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-stations-code-in-city 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