Fetch the world-record / top-N leaderboard for a specific game category. Returns ranked runs with finish times (ISO-8601 duration plus seconds), run date, players, and weblink. Get game_id from search_games and category_id from get_categories. Example: get_leaderboard({ game_id: "o1y9wo6q", categ...
AI agents call get_leaderboard to retrieve information from Mcp Speedrun without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
top | number | — | Number of top-ranked runs to return (default 10) |
_apiKey | string | — | Optional speedrun.com API key for authenticated access; omit to use the shared platform key |
game_id | string | Yes | Speedrun.com game ID, as returned by search_games |
category_id | string | Yes | Speedrun.com category ID, as returned by get_categories |
Parameters from the server's own tool schema.
This tool retrieves and queries publicly available leaderboard data from Speedrun.com without creating, modifying, deleting, or executing any operations. It is a straightforward read-only operation that poses minimal security risk even if misused by an AI agent, as the worst outcome would be retrieving leaderboard information the agent is already authorized to access via the public API.
From the tool's definition Tool description states 'Fetch the world-record / top-N leaderboard' and 'Returns ranked runs with finish times, run date, players, and weblink.' The verb 'Fetch' and 'Returns' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Fetch the world-record / top-N leaderboard for a specific game category. Returns ranked runs with finish times (ISO-8601 duration plus seconds), run date, players, and weblink. Get game_id from search_games and category_id from get_categories. Example: get_leaderboard({ game_id: "o1y9wo6q", category_id: "7kjpp4k3", top: 10 }). It is categorised as a Read tool in the Mcp Speedrun MCP Server, which means it retrieves data without modifying state.
get_leaderboard accepts 4 parameters: top, _apiKey, game_id, category_id. Required: game_id, category_id. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Speedrun MCP server in PolicyLayer and add a rule for get_leaderboard: 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 Mcp Speedrun. Nothing to install.
get_leaderboard 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_leaderboard 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_leaderboard. 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_leaderboard is provided by the Mcp Speedrun MCP server (pipeworx-io/mcp-speedrun). 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 →