New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get-interline-tickets

查询12306中转余票信息。尚且只支持查询前十条。

SERVER12306 Ticket Search Server SOURCEDeniseLewis200081/rail
Low RISK CLASS
Category Read
Parameters 90 required
Recommended Allowedsee the rule below
Registry record Grade A, identity unverified Pull the record →

This record as markdown: /tools/deniselewis200081-rail/get-interline-tickets.md

What get-interline-tickets does on 12306 Ticket Search Server

AI agents call get-interline-tickets 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.

ParameterTypeRequiredDescription
date string 查询日期,格式为 "yyyy-MM-dd"。如果用户提供的是相对日期(如“明天”),请务必先调用 `get-current-date` 接口获取当前日期,并计算出目标日期。
showWZ boolean 是否显示无座车,默认不显示无座车。
sortFlag string 排序方式,默认为空,即不排序。仅支持单一标识。可选标志:[startTime(出发时间从早到晚), arriveTime(抵达时间从早到晚), duration(历时从短到长)]
toStation string 出发地的 `station_code` 。必须是通过 `get-station-code-by-names` 或 `get-station-code-of-citys` 接口查询得到的编码,严禁直接使用中文地名。
limitedNum number 返回的中转余票数量限制,默认为10。
fromStation string 出发地的 `station_code` 。必须是通过 `get-station-code-by-names` 或 `get-station-code-of-citys` 接口查询得到的编码,严禁直接使用中文地名。
sortReverse boolean 是否逆向排序结果,默认为false。仅在设置了sortFlag时生效。
middleStation string 中转地的 `station_code` ,可选。必须是通过 `get-station-code-by-names` 或 `get-station-code-of-citys` 接口查询得到的编码,严禁直接使用中文地名。
trainFilterFlags string 车次筛选条件,默认为空。从以下标志中选取多个条件组合[G(高铁/城际),D(动车),Z(直达特快),T(特快),K(快速),O(其他),F(复兴号),S(智能动车组)]

Parameters from the server's own tool schema.

Why get-interline-tickets is rated Low

This tool performs a passive data retrieval operation—querying transfer ticket availability from the 12306 railway system. It has no side effects on the system or data. Even if an AI agent misuses it by making excessive queries, the blast radius is minimal (rate limiting, temporary blocks). No financial transactions, data modifications, deletions, or code execution are involved.

From the tool's definition Tool name 'get-interline-tickets' and description '查询12306中转余票信息。尚且只支持查询前十条' (Query 12306 transfer ticket availability information.

Questions about get-interline-tickets

What does the get-interline-tickets tool do? +

查询12306中转余票信息。尚且只支持查询前十条。. It is categorised as a Read tool in the 12306 Ticket Search Server MCP Server, which means it retrieves data without modifying state.

What parameters does get-interline-tickets accept? +

get-interline-tickets accepts 9 parameters: date, showWZ, sortFlag, toStation, limitedNum, fromStation, sortReverse, middleStation, trainFilterFlags. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get-interline-tickets? +

Register the 12306 Ticket Search Server MCP server in PolicyLayer and add a rule for get-interline-tickets: 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.

What risk level is get-interline-tickets? +

get-interline-tickets is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get-interline-tickets? +

Yes. Add a rate_limit block to the get-interline-tickets 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.

How do I block get-interline-tickets completely? +

Set action: deny in the PolicyLayer policy for get-interline-tickets. 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.

What MCP server provides get-interline-tickets? +

get-interline-tickets 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of 12306 Ticket Search Server's. Pull the full record:

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.