Returns the prices each day of a given item for the previous 180 days. This is useful for seeing the price trends of an item over time. Usefull for when someone asks all price history of an item. Examples: - Single: "Price history of a dragon scimitar?" - Multi comparison: "Compare all price hist...
AI agents call get_item_price_history to retrieve information from Runescape without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
gameMode | string | Yes | The mode of the game, this can be "osrs" or "rs". osrs = old school runescape, rs = runescape |
itemName | string | Yes | The name of the item you want to get the price history for. |
Parameters from the server's own tool schema.
This tool retrieves historical price information for items in RuneScape, which is a pure read operation. It queries and returns data without creating, modifying, deleting, or executing any operations. The tool has no blast radius for misuse - an AI agent querying item prices poses no risk to data integrity or system state.
From the tool's definition Returns the prices each day of a given item for the previous 180 days. Described as retrieving historical price data without modifying any data or triggering side effects.
Attacks that exploit this kind of access
Returns the prices each day of a given item for the previous 180 days. This is useful for seeing the price trends of an item over time. Usefull for when someone asks all price history of an item. Examples: - Single: "Price history of a dragon scimitar?" - Multi comparison: "Compare all price history of a dragon scimitar and a rune scimitar" - "All prices for a dragon scimitar" - "Rune scimitar price on 1 april 2025". It is categorised as a Read tool in the Runescape MCP Server, which means it retrieves data without modifying state.
get_item_price_history accepts 2 parameters: gameMode, itemName. Required: gameMode, itemName. The full parameter table on this page comes from the server's own tool schema.
Register the Runescape MCP server in PolicyLayer and add a rule for get_item_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 Runescape. Nothing to install.
get_item_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_item_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_item_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_item_price_history is provided by the Runescape MCP server (mcp-server-runescape). 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 →