Search the Speedrun.com database for games by name. Returns matching games with their ID (needed for get_categories and get_leaderboard), abbreviation, release year, and weblink. Example: search_games({ query: "super mario 64", max: 5 })
AI agents call search_games 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 |
|---|---|---|---|
max | number | — | Maximum number of games to return (default 10) |
query | string | Yes | Game name or keyword to search for, e.g. "super mario 64", "celeste" |
_apiKey | string | — | Optional speedrun.com API key for authenticated access; omit to use the shared platform key |
Parameters from the server's own tool schema.
This tool retrieves public game metadata from Speedrun.com without modifying, deleting, or executing any operations. It is a straightforward read operation that poses minimal risk even if misused by an AI agent, as the worst outcome would be querying for irrelevant games or excessive lookups.
From the tool's definition Tool description states it 'Search[es] the Speedrun.com database for games by name' and 'Returns matching games with their ID, abbreviation, release year, and weblink.' The verb 'search' combined with 'returns' indicates query/retrieval operations with no…
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
Search the Speedrun.com database for games by name. Returns matching games with their ID (needed for get_categories and get_leaderboard), abbreviation, release year, and weblink. Example: search_games({ query: "super mario 64", max: 5 }). It is categorised as a Read tool in the Mcp Speedrun MCP Server, which means it retrieves data without modifying state.
search_games accepts 3 parameters: max, query, _apiKey. Required: query. 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 search_games: 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.
search_games 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 search_games 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 search_games. 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.
search_games 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 →