check_price_changes

Returns all LLM pricing changes recorded since a given date, optionally filtered to a specific model or provider.

Server Whichmodel-mcp which-model/whichmodel-mcp
Category Read
Risk class Low
Parameters 00 required

What check_price_changes does on Whichmodel-mcp

AI agents call check_price_changes to retrieve information from Whichmodel-mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why check_price_changes needs a policy

The tool retrieves and presents pricing information from a database without creating, modifying, deleting, executing code, or handling financial transactions. It is purely informational and read-only, making it a Read category tool with low severity since misuse would only expose pricing data already available through other means in this server's context.

From the tool's definition Returns all LLM pricing changes recorded since a given date, optionally filtered to a specific model or provider — this is a retrieval/query operation that reads historical pricing data with no side effects.

Questions about check_price_changes

What does the check_price_changes tool do? +

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 MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_price_changes? +

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-mcp. Nothing to install.

What risk level is check_price_changes? +

check_price_changes is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_price_changes? +

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.

How do I block check_price_changes completely? +

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.

What MCP server provides check_price_changes? +

check_price_changes is provided by the Whichmodel- MCP server (which-model/whichmodel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.