# get-station-by-telecode

通过车站的 station_telecode 查询车站的详细信息，包括名称、拼音、所属城市等。此接口主要用于在已知 telecode 的情况下获取更完整的车站数据，或用于特殊查询及调试目的。一般用户对话流程中较少直接触发。

Agent View of the PolicyLayer registry record for `get-station-by-telecode`. HTML page: https://policylayer.com/tools/deniselewis200081-rail/get-station-by-telecode

## Facts

- Tool: `get-station-by-telecode`
- 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 |
| --- | --- | --- | --- |
| `stationTelecode` | string | no | 车站的 `station_telecode` (3位字母编码) |

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-station-by-telecode",
    "arguments": {}
  }
}
```

## 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 own definition: "Tool description states it 'queries station detailed information' (查询车站的详细信息) by telecode, including name, pinyin, and city."

## Use case

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.

## 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-station-by-telecode": {}
  }
}
```

## 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-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-stations-code-in-city` — Read — https://policylayer.com/tools/deniselewis200081-rail/get-stations-code-in-city.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