This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/untappd-get-brewery.md
What untappd_get_brewery does on UnClick
AI agents call untappd_get_brewery 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 |
|---|---|---|---|
api_key | string | — | |
brewery_id | number | Yes |
Parameters from the server's own tool schema.
Why untappd_get_brewery is rated Low
This tool queries and retrieves brewery information from the Untappd platform. The verb 'Get' and the absence of any modification, deletion, or execution language confirm this is a read-only operation. There is no financial impact, code execution, or destructive capability. Severity is low because unauthorized or excessive use retrieves only public brewery metadata with minimal harm potential.
From the tool's definition Tool name 'untappd_get_brewery' and description 'Get details for a brewery on Untappd' indicate a retrieval operation with no side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs untappd_get_brewery 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 untappd_get_brewery, this is the rule to start with:
untappd_get_brewery 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 untappd_get_brewery call is checked against it from then on.
Questions about untappd_get_brewery
Get details for a brewery on Untappd. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
untappd_get_brewery accepts 2 parameters: api_key, brewery_id. Required: brewery_id. 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 untappd_get_brewery: 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.
untappd_get_brewery 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 untappd_get_brewery 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 untappd_get_brewery. 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.
untappd_get_brewery 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