Fetches all available travel options between two locations
AI agents call get_routes to retrieve information from TravelChecker without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries travel route data without modifying, deleting, or executing any external operations. It is a straightforward information retrieval function that presents options to users without causing any changes to system state or external services. The low severity reflects that misuse would only result in unwanted information access, not data loss, execution, or financial impact.
From the tool's definition Tool name 'get_routes' and description 'Fetches all available travel options' indicate a retrieval operation with no side effects. The verb 'Fetches' is consistent with Read category operations like search, list, and get.
Attacks that exploit this kind of access
Fetches all available travel options between two locations. It is categorised as a Read tool in the TravelChecker MCP Server, which means it retrieves data without modifying state.
Register the TravelChecker MCP server in PolicyLayer and add a rule for get_routes: 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 TravelChecker. Nothing to install.
get_routes 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_routes 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_routes. 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_routes is provided by the TravelChecker MCP server (tharun99856/travelchecker). 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 →