查詢指定車班的座位狀況
AI agents call get_thsr_train_seat_status to retrieve information from THSRC MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays seat availability information for a specific train. It is a read-only query operation with no side effects—no data is created, modified, deleted, or executed. The blast radius of misuse is minimal; an AI agent could only retrieve seat information, which poses no security, financial, or operational risk.
From the tool's definition Tool name 'get_thsr_train_seat_status' and description '查詢指定車班的座位狀況' (query seat status of specified train) indicate a retrieval operation that queries real-time seat availability data without modifying any state.
Attacks that exploit this kind of access
查詢指定車班的座位狀況. It is categorised as a Read tool in the THSRC MCP Server MCP Server, which means it retrieves data without modifying state.
Register the THSRC MCP Server MCP server in PolicyLayer and add a rule for get_thsr_train_seat_status: 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 THSRC MCP Server. Nothing to install.
get_thsr_train_seat_status 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_thsr_train_seat_status 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_thsr_train_seat_status. 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_thsr_train_seat_status is provided by the THSRC MCP Server MCP server (physictim/thsrc_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →