bgg_game_details
Get full details for a board game by its BGG ID - name, year, rating, players, playtime, description, categories, and mechanics.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/bgg-game-details.md
What bgg_game_details does on UnClick
AI agents call bgg_game_details 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 |
|---|---|---|---|
gameId | string | Yes | BoardGameGeek game ID |
Parameters from the server's own tool schema.
Why bgg_game_details is rated Low
This is a straightforward data retrieval tool that fetches read-only information from BoardGameGeek about a specific game. There are no capabilities to modify data, execute commands, delete records, or commit financial transactions. The only action is retrieving and returning existing game metadata.
From the tool's definition Tool description states 'Get full details for a board game' - a retrieval operation that queries board game data by ID and returns informational fields (name, year, rating, players, playtime, description, categories, mechanics) with no modification or side…
Attacks that exploit this kind of access
The rule that runs bgg_game_details 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 bgg_game_details, this is the rule to start with:
bgg_game_details 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 bgg_game_details call is checked against it from then on.
Questions about bgg_game_details
Get full details for a board game by its BGG ID - name, year, rating, players, playtime, description, categories, and mechanics. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
bgg_game_details accepts 1 parameter: gameId. Required: gameId. 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 bgg_game_details: 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.
bgg_game_details 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 bgg_game_details 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 bgg_game_details. 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.
bgg_game_details 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