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:
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.
This tool retrieves historical pricing data from the RuneScape game database. It performs a read-only query operation that does not create, modify, delete, execute code, or involve financial transactions. The tool simply returns historical information that already exists. While the data relates to in-game item prices, accessing this data poses no direct risk as it is informational only.
From the tool's definition The tool 'returns the prices each day of a given item for the previous 180 days' and is described as useful for 'seeing the price trends of an item over time.' This is a pure retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_item_price_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Runescape, and nothing reaches the server without passing your rules. This is the rule we recommend for get_item_price_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_item_price_history": {}
}
}get_item_price_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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:. It is categorised as a Read tool in the Runescape MCP Server, which means it retrieves data without modifying state.
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 (stjepko-xyz/mcp-server-runescape). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Runescape, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Runescape tools catalogued and risk-classified — across an index of 43,000+ MCP servers.