This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/bgg-search.md
What bgg_search does on UnClick
AI agents call bgg_search 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 |
|---|---|---|---|
type | string | — | Type of item to search for (default: boardgame) |
query | string | Yes | Game name to search for |
Parameters from the server's own tool schema.
Why bgg_search is rated Low
This tool performs a search operation on BoardGameGeek, a public board game database. It retrieves information based on search criteria (name) but does not create, modify, delete, or execute any operations. No side effects or external system state changes occur. This is a standard read-only data retrieval action with minimal security risk.
From the tool's definition Tool name 'bgg_search' and description 'Search BoardGameGeek for board games by name' indicate a query operation that retrieves data without modification.
Attacks that exploit this kind of access
The rule that runs bgg_search 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_search, this is the rule to start with:
bgg_search 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_search call is checked against it from then on.
Questions about bgg_search
Search BoardGameGeek for board games by name. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
bgg_search accepts 2 parameters: type, query. Required: query. 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_search: 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_search 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_search 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_search. 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_search 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