Returns a player's rank, level and experience or score in an activity. Examples: - Single: "What rank is Zezima?" - Multi comparison: "Compare Zezima and Lynx Titan" - "What rank is Zezima on runescape?" - "How much experience does Lynx Titan have overall?" - "Iron Hyger ironman?"
AI agents call get_player_hiscore 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 |
|---|---|---|---|
type | string | — | The type of game you want to get the hiscore for. Leave empty if no type is specified. Types: ironman, hardcore_ironman, ultimate, deadman, seasonal (leagues), |
gameMode | string | Yes | The mode of the game, this can be "osrs" or "rs". osrs = old school runescape, rs = runescape |
playerName | string | Yes | The name of the player you want to get the hiscore for. |
Parameters from the server's own tool schema.
This tool retrieves player statistics and rankings from RuneScape without any side effects, data modification, or external operation triggering. It is a pure query/read operation over publicly available player data.
From the tool's definition Tool description states it 'Returns a player's rank, level and experience or score in an activity.' The examples show queries like 'What rank is Zezima?' and 'How much experience does Lynx Titan have overall?' which are informational lookups with no…
Attacks that exploit this kind of access
Returns a player's rank, level and experience or score in an activity. Examples: - Single: "What rank is Zezima?" - Multi comparison: "Compare Zezima and Lynx Titan" - "What rank is Zezima on runescape?" - "How much experience does Lynx Titan have overall?" - "Iron Hyger ironman?". It is categorised as a Read tool in the Runescape MCP Server, which means it retrieves data without modifying state.
get_player_hiscore accepts 3 parameters: type, gameMode, playerName. Required: gameMode, playerName. 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_player_hiscore: 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_player_hiscore 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_player_hiscore 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_player_hiscore. 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_player_hiscore 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 →