Retrieves available transportation options between two points
AI agents call get_transport_options to retrieve information from Server Travelplanner without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
date | string | Yes | Travel date (YYYY-MM-DD) |
origin | string | Yes | Starting point |
destination | string | Yes | Destination point |
Parameters from the server's own tool schema.
This tool retrieves transportation information for travel planning purposes. The verb 'retrieves' explicitly indicates a read-only operation. No data is created, modified, deleted, or executed. The tool serves an informational purpose in itinerary planning and poses minimal security risk.
From the tool's definition Tool name 'get_transport_options' and description 'Retrieves available transportation options between two points' indicate a query operation that fetches data without modification or side effects.
Risk signalsAccepts file system path (destination)
Attacks that exploit this kind of access
Retrieves available transportation options between two points. It is categorised as a Read tool in the Server Travelplanner MCP Server, which means it retrieves data without modifying state.
get_transport_options accepts 3 parameters: date, origin, destination. Required: date, origin, destination. The full parameter table on this page comes from the server's own tool schema.
Register the Server Travelplanner MCP server in PolicyLayer and add a rule for get_transport_options: 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 Server Travelplanner. Nothing to install.
get_transport_options 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_transport_options 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_transport_options. 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_transport_options is provided by the Server Travelplanner MCP server (@gongrzhe/server-travelplanner-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 →