speedrun_list_runs
List speedruns with optional filters for game, category, user, or status.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/speedrun-list-runs.md
What speedrun_list_runs does on UnClick
AI agents call speedrun_list_runs to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
max | number | — | |
game | string | — | Game ID |
user | string | — | User ID |
status | string | — | new, verified, or rejected |
orderby | string | — | date, submitted, status, game, category, level, platform, region, emulated, or weblink |
category | string | — | |
direction | string | — | asc or desc |
Parameters from the server's own tool schema.
Why speedrun_list_runs is rated Low
This tool queries and returns speedrun data based on optional filter parameters. It retrieves information without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an agent could retrieve unfiltered speedrun data but cannot change state or cause harm.
From the tool's definition Tool description states 'List speedruns with optional filters' — a retrieval operation with no modification or side effects. The verb 'list' is explicitly a Read operation.
Attacks that exploit this kind of access
The rule that runs speedrun_list_runs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For speedrun_list_runs, this is the rule to start with:
speedrun_list_runs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every speedrun_list_runs call is checked against it from then on.
Questions about speedrun_list_runs
List speedruns with optional filters for game, category, user, or status. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
speedrun_list_runs accepts 7 parameters: max, game, user, status, orderby, category, direction. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for speedrun_list_runs: 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 UnClick. Nothing to install.
speedrun_list_runs 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 speedrun_list_runs 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 speedrun_list_runs. 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.
speedrun_list_runs is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue