Side-by-side comparison of 2–5 specific LLMs by pricing, quality tier, capabilities, and projected costs.
AI agents call compare_models to retrieve information from Whichmodel without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure lookup/analysis tool that retrieves and displays comparative information about LLM models. It has no side effects, does not execute code or commands, does not modify data, and does not process financial transactions. The worst misuse outcome is an AI agent receiving incorrect cost-comparison guidance, which is information-based risk only.
From the tool's definition Tool performs 'side-by-side comparison' and returns 'pricing, quality tier, capabilities, and projected costs' — data retrieval and display only. No modification, execution, deletion, or financial transaction occurs.
Attacks that exploit this kind of access
Side-by-side comparison of 2–5 specific LLMs by pricing, quality tier, capabilities, and projected costs. It is categorised as a Read tool in the Whichmodel MCP Server, which means it retrieves data without modifying state.
Register the Whichmodel MCP server in PolicyLayer and add a rule for compare_models: 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 Whichmodel. Nothing to install.
compare_models 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_models 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_models. 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_models is provided by the Whichmodel MCP server (simonamsharp/routewise-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 →