Get full metadata for a single game by its TheGamesDB id, including the front boxart image URL. Example: get_game({ id: 108139 })
AI agents call get_game 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 |
|---|---|---|---|
id | number | string | Yes | TheGamesDB game id, e.g. 108139 |
_apiKey | string | — | Optional TheGamesDB API key. Omit to use the shared Pipeworx platform key. |
Parameters from the server's own tool schema.
This tool retrieves and returns game metadata and image URLs from TheGamesDB without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with minimal security risk—the worst-case scenario is exposure to a game database query, which carries no destructive, financial, or code-execution risk.
From the tool's definition Tool description: 'Get full metadata for a single game by its TheGamesDB id' — uses 'Get' verb and performs a query-only operation retrieving game data and image URLs with no modifications or side effects.
Attacks that exploit this kind of access
Get full metadata for a single game by its TheGamesDB id, including the front boxart image URL. Example: get_game({ id: 108139 }). It is categorised as a Read tool in the Thegamesdb MCP Server, which means it retrieves data without modifying state.
get_game accepts 2 parameters: id, _apiKey. Required: id. 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 get_game: 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.
get_game 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_game 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_game. 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_game 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 →