This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/brewery-search.md
What brewery_search does on UnClick
AI agents call brewery_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 |
|---|---|---|---|
query | string | Yes | |
per_page | number | — | Results per page (max 50) |
Parameters from the server's own tool schema.
Why brewery_search is rated Low
This tool retrieves or queries brewery data based on a search parameter (name). It is a read-only operation that does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal—an AI agent could only retrieve brewery information that is already publicly available.
From the tool's definition Tool name is 'brewery_search' and description states 'Search breweries by name.' This is a query/search operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs brewery_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 brewery_search, this is the rule to start with:
brewery_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 brewery_search call is checked against it from then on.
Questions about brewery_search
Search breweries by name. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
brewery_search accepts 2 parameters: query, per_page. 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 brewery_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.
brewery_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 brewery_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 brewery_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.
brewery_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