cocktail_filter_by_ingredient
Filter cocktails by ingredient.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/cocktail-filter-by-ingredient.md
What cocktail_filter_by_ingredient does on UnClick
AI agents call cocktail_filter_by_ingredient 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 |
|---|---|---|---|
ingredient | string | Yes | e.g. Vodka, Rum, Gin, Whiskey |
Parameters from the server's own tool schema.
Why cocktail_filter_by_ingredient is rated Low
This tool retrieves or queries cocktail data based on ingredient filters. It is a straightforward read operation that returns matching cocktails without creating, modifying, deleting, or executing any external actions. The low severity reflects minimal risk even if misused by an AI agent.
From the tool's definition Tool name indicates 'filter' operation; description states 'Filter cocktails by ingredient' which is a query/retrieval action with no modifications or side effects.
Attacks that exploit this kind of access
The rule that runs cocktail_filter_by_ingredient 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_filter_by_ingredient, this is the rule to start with:
cocktail_filter_by_ingredient 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_filter_by_ingredient call is checked against it from then on.
Questions about cocktail_filter_by_ingredient
Filter cocktails by ingredient. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
cocktail_filter_by_ingredient accepts 1 parameter: ingredient. Required: ingredient. 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_filter_by_ingredient: 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_filter_by_ingredient 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_filter_by_ingredient 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_filter_by_ingredient. 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_filter_by_ingredient 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