// SCAN REPORT

12306 Ticket Search Server

8 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 5 Aug 2026

0 can modify or destroy data

8 read-only

8 tools total

Community server · catalogue entry checked 12/06/2026 · full schemas captured for 7 of 8 tools

How to control 12306 Ticket Search Server ↓

TOOL MAP

What 12306 Ticket Search Server exposes to your agents

Read (8) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What 12306 Ticket Search Server costs in tokens

1,839 tokens of tool definitions, loaded on every request

0.9% of a 200k context window

536 heaviest tool: get-interline-tickets

Full per-tool breakdown → Model it in the token calculator →

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control 12306 Ticket Search Server

PolicyLayer is an MCP gateway — it sits between your AI agents and 12306 Ticket Search Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "get-current-date": {
    "limits": [
      {
        "counter": "get-current-date_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register 12306 Ticket Search Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON 12306 TICKET SEARCH →

Instant setup, no code required.

FULL CATALOGUE

All 8 12306 Ticket Search Server tools

READ 8 tools

Read get-current-date 获取当前日期，以上海时区（Asia/Shanghai, UTC+8）为准，返回格式为 "yyyy-MM-dd"。主要用于解析用户提到的相对日期（如“明天”、“下周三”），为其他需要日期的接口提供准确的日期输入。 Read get-interline-tickets 查询12306中转余票信息。尚且只支持查询前十条。 Read get-station-by-telecode 通过车站的 station_telecode 查询车站的详细信息，包括名称、拼音、所属城市等。此接口主要用于在已知 telecode 的情况下获取更完整的车站数据，或用于特殊查询及调试目的。一般用户对话流程中较少直接触发 Read get-station-code-by-names 通过具体的中文车站名查询其 station_code 和车站名。此接口主要用于在用户提供具体车站名作为出发地或到达地时，为接口准备 station_code 参数。 Read get-station-code-of-citys 通过中文城市名查询代表该城市的 station_code。此接口主要用于在用户提供城市名作为出发地或到达地时，为接口准备 station_code 参数。 Read get-stations-code-in-city 通过中文城市名查询该城市所有火车站的名称及其对应的 station_code，结果是一个包含多个车站信息的列表。 Read get-tickets 查询12306余票信息。 Read get-train-route-stations 查询特定列车车次在指定区间内的途径车站、到站时间、出发时间及停留时间等详细经停信息。当用户询问某趟具体列车的经停站时使用此接口。

FAQ

Questions about 12306 Ticket Search Server

Is the 12306 Ticket Search Server MCP server safe to use without restrictions? +

The 12306 Ticket Search Server server is primarily read-only with 8 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the 12306 Ticket Search Server MCP server expose? +

8 tools across 1 categories: Read. 8 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on 12306 Ticket Search Server? +

Register the 12306 Ticket Search Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every 12306 Ticket Search Server tool call.

Deterministic rules across all 8 12306 Ticket Search Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON 12306 TICKET SEARCH →

Instant setup, no code required.

8 12306 Ticket Search Server tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from 12306 Ticket Search Server's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →