bgg_user_collection
Get a BGG user's game collection filtered by status (owned, wishlist, or played).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/bgg-user-collection.md
What bgg_user_collection does on UnClick
AI agents call bgg_user_collection 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 |
|---|---|---|---|
status | string | — | Collection filter (default: owned) |
username | string | Yes | BGG username |
Parameters from the server's own tool schema.
Why bgg_user_collection is rated Low
This tool retrieves publicly available BoardGameGeek user collection data based on specified filters (owned, wishlist, or played status). It has no side effects, does not modify data, execute code, or produce irreversible changes. The only risk is potential privacy concerns if user collection data is sensitive, but the operation itself is purely a read/query function.
From the tool's definition Tool description states 'Get a BGG user's game collection filtered by status' - the verb 'Get' and the filtering operation indicate data retrieval with no modification, deletion, or execution of arbitrary operations.
Attacks that exploit this kind of access
The rule that runs bgg_user_collection 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_user_collection, this is the rule to start with:
bgg_user_collection 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_user_collection call is checked against it from then on.
Questions about bgg_user_collection
Get a BGG user's game collection filtered by status (owned, wishlist, or played). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
bgg_user_collection accepts 2 parameters: status, username. Required: username. 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_user_collection: 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_user_collection 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_user_collection 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_user_collection. 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_user_collection 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