Search the TheGamesDB video-game database by title. Returns matching games with platform name, release date, players, rating, and a short overview. Example: search_games({ name: "zelda", limit: 10 })
AI agents call search_games to retrieve information from Thegamesdb without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Game title or keyword to search for, e.g. "zelda", "halo", "final fantasy" |
limit | number | — | Maximum number of results to return (default 15) |
_apiKey | string | — | Optional TheGamesDB API key. Omit to use the shared Pipeworx platform key. |
Parameters from the server's own tool schema.
This tool only retrieves publicly available video game metadata from TheGamesDB. It has no side effects, cannot modify data, execute code, or access sensitive resources. The blast radius of misuse is minimal—an agent could only perform excessive queries or retrieve game information already public.
From the tool's definition Tool searches and returns game data with no modification capability: 'Search the TheGamesDB video-game database by title.
Attacks that exploit this kind of access
Search the TheGamesDB video-game database by title. Returns matching games with platform name, release date, players, rating, and a short overview. Example: search_games({ name: "zelda", limit: 10 }). It is categorised as a Read tool in the Thegamesdb MCP Server, which means it retrieves data without modifying state.
search_games accepts 3 parameters: name, limit, _apiKey. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Thegamesdb 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 Thegamesdb. 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 Thegamesdb MCP server (https://gateway.pipeworx.io/thegamesdb/mcp). 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 →