Returns the current price and price trends information on tradeable items in the Grand Exchange, the category, item image and examine for the given item. Examples: - Single:
AI agents call get_item_details 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 is a read-only data retrieval tool that queries RuneScape Grand Exchange information. It performs no mutations, deletions, code execution, or financial transactions—merely fetches and presents existing item metadata and pricing information.
From the tool's definition Tool returns current price, price trends, category, item image, and examine text for Grand Exchange items. All operations are queries with no side effects: 'Returns' (not creates/modifies/deletes) data about in-game items.
Documented attack patterns abuse exactly the kind of access get_item_details 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_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_item_details": {}
}
}get_item_details 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 current price and price trends information on tradeable items in the Grand Exchange, the category, item image and examine for the given 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_details: 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_details 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_details 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_details. 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_details 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.