This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/brewery-random.md
What brewery_random does on UnClick
AI agents call brewery_random 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 |
|---|---|---|---|
size | number | — | Number of breweries (1-50, default 1) |
Parameters from the server's own tool schema.
Why brewery_random is rated Low
This tool performs a simple data retrieval operation with no side effects. It fetches random brewery data from a database, analogous to a read-only search or list query. There is no indication of write, delete, or execute capabilities. The blast radius of misuse is minimal—an agent could only retrieve redundant brewery information.
From the tool's definition Tool name 'brewery_random' and description 'Get random breweries' indicate a retrieval operation that queries a breweries database to fetch random entries. No data modification, deletion, or execution of arbitrary operations occurs.
Attacks that exploit this kind of access
The rule that runs brewery_random 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_random, this is the rule to start with:
brewery_random 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_random call is checked against it from then on.
Questions about brewery_random
Get random breweries. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
brewery_random accepts 1 parameter: size. 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_random: 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_random 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_random 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_random. 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_random 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