This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/cocktail-search.md
What cocktail_search does on UnClick
AI agents call cocktail_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 |
Parameters from the server's own tool schema.
Why cocktail_search is rated Low
This tool performs a straightforward search/retrieval operation (Read category) with no side effects. The search functionality has minimal blast radius if misused—an AI agent could only retrieve cocktail recipe information, which poses no security, financial, or operational risk. Severity is low due to the benign nature of the data being accessed.
From the tool's definition Tool name 'cocktail_search' and description 'Search for cocktails/drinks by name' indicate a query operation that retrieves data without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
The rule that runs cocktail_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 cocktail_search, this is the rule to start with:
cocktail_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 cocktail_search call is checked against it from then on.
Questions about cocktail_search
Search for cocktails/drinks by name. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
cocktail_search accepts 1 parameter: 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 cocktail_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.
cocktail_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 cocktail_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 cocktail_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.
cocktail_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