Historical pricing time-series for a model or provider. Each point is a dated snapshot of the per-Mtok rates.
AI agents call get_price_history to retrieve information from Modelmeter without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
model | string | — | Model id to fetch history for. |
since | string | — | ISO date (YYYY-MM-DD); only points on/after this date. |
until | string | — | ISO date (YYYY-MM-DD); only points on/before this date. |
provider | string | — | Provider id to fetch history for (all its models). |
Parameters from the server's own tool schema.
This tool retrieves and queries historical pricing data. It performs a lookup/fetch operation with no capability to modify pricing, trigger financial transactions, execute code, or delete data. The blast radius of misuse is minimal—an agent could only access historical pricing information that is already public. This is a straightforward Read operation.
From the tool's definition Tool name 'get_price_history' and description 'Historical pricing time-series for a model or provider. Each point is a dated snapshot of the per-Mtok rates' indicate retrieval of historical data without modification or side effects.
Attacks that exploit this kind of access
Historical pricing time-series for a model or provider. Each point is a dated snapshot of the per-Mtok rates. It is categorised as a Read tool in the Modelmeter MCP Server, which means it retrieves data without modifying state.
get_price_history accepts 4 parameters: model, since, until, provider. The full parameter table on this page comes from the server's own tool schema.
Register the Modelmeter MCP server in PolicyLayer and add a rule for get_price_history: 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 Modelmeter. Nothing to install.
get_price_history 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_price_history 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_price_history. 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_price_history is provided by the Modelmeter MCP server (https://modelmeter.xyz/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_price_history is one line of Modelmeter's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →