brewery_list
List breweries, optionally filtered by city, state, or type.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/brewery-list.md
What brewery_list does on UnClick
AI agents call brewery_list 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 |
|---|---|---|---|
city | string | — | |
page | number | — | |
type | string | — | micro, nano, regional, brewpub, large, planning, bar, contract, proprietor, closed |
state | string | — | |
per_page | number | — |
Parameters from the server's own tool schema.
Why brewery_list is rated Low
This tool retrieves public information about breweries with optional filters. It performs a read-only query operation with no ability to modify, delete, or execute code. The filtering parameters (city, state, type) are simple search criteria. There is no financial impact, no destructive capability, and no code execution. Misuse would result in minimal harm beyond retrieving publicly available information.
From the tool's definition Tool name 'brewery_list' and description 'List breweries, optionally filtered by city, state, or type' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs brewery_list 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_list, this is the rule to start with:
brewery_list 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_list call is checked against it from then on.
Questions about brewery_list
List breweries, optionally filtered by city, state, or type. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
brewery_list accepts 5 parameters: city, page, type, state, per_page. 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_list: 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_list 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_list 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_list. 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_list 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