# get-stations-code-in-city

通过中文城市名查询该城市 所有 火车站的名称及其对应的 station_code，结果是一个包含多个车站信息的列表。

Agent View of the PolicyLayer registry record for `get-stations-code-in-city`. HTML page: https://policylayer.com/tools/deniselewis200081-rail/get-stations-code-in-city

## Facts

- Tool: `get-stations-code-in-city`
- Server: 12306 Ticket Search Server (`DeniseLewis200081/rail`) — https://policylayer.com/tools/deniselewis200081-rail.md
- Homepage: https://github.com/DeniseLewis200081/rail
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 1
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `city` | string | no | 中文城市名称，例如："北京", "上海" |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get-stations-code-in-city",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches 12306 Ticket Search Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-stations-code-in-city": {}
  }
}
```

## Other tools on 12306 Ticket Search Server (7)

- `get-current-date` — Read — https://policylayer.com/tools/deniselewis200081-rail/get-current-date.md
- `get-interline-tickets` — Read — https://policylayer.com/tools/deniselewis200081-rail/get-interline-tickets.md
- `get-station-by-telecode` — Read — https://policylayer.com/tools/deniselewis200081-rail/get-station-by-telecode.md
- `get-station-code-by-names` — Read — https://policylayer.com/tools/deniselewis200081-rail/get-station-code-by-names.md
- `get-station-code-of-citys` — Read — https://policylayer.com/tools/deniselewis200081-rail/get-station-code-of-citys.md
- `get-tickets` — Read — https://policylayer.com/tools/deniselewis200081-rail/get-tickets.md
- `get-train-route-stations` — Read — https://policylayer.com/tools/deniselewis200081-rail/get-train-route-stations.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=deniselewis200081-rail · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/deniselewis200081-rail