Takes raw routes and applies preference weights to score them
AI agents call compare_options 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.
The tool performs a pure data transformation and comparison function—it reads routes, applies weights, and produces scored output. There are no side effects, no data modification, no external execution, and no irreversible actions. This is a classic Read operation: retrieval and analysis of data with no side effects.
From the tool's definition Tool 'compare_options' takes raw routes and applies preference weights to score them. This is a computational operation that reads input data (routes and weights), performs scoring calculations, and returns results without modifying, deleting, or executing…
Attacks that exploit this kind of access
Takes raw routes and applies preference weights to score them. 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 compare_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 TravelChecker. Nothing to install.
compare_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 compare_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 compare_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.
compare_options 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 →