Returns all LLM pricing changes recorded since a given date, optionally filtered to a specific model or provider.
AI agents call check_price_changes 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 tool purely queries historical pricing data and returns information. It has no side effects, does not modify or delete data, does not execute code or commands, and does not involve financial transactions. It is a straightforward Read operation with minimal risk if misused by an autonomous agent.
From the tool's definition Tool description states it 'Returns all LLM pricing changes recorded since a given date' — a data retrieval operation with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Returns all LLM pricing changes recorded since a given date, optionally filtered to a specific model or provider. 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 check_price_changes: 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.
check_price_changes 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 check_price_changes 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 check_price_changes. 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.
check_price_changes 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 →