This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/cocktail-get-by-id.md
What cocktail_get_by_id does on UnClick
AI agents call cocktail_get_by_id 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 |
|---|---|---|---|
id | string | Yes | TheCocktailDB drink ID |
Parameters from the server's own tool schema.
Why cocktail_get_by_id is rated Low
This tool retrieves cocktail information by ID, which is a read-only query operation. It does not create, modify, delete, execute code, or involve financial transactions. The blast radius of misuse is minimal—an attacker could only access cocktail recipe data.
From the tool's definition Tool name 'cocktail_get_by_id' and description 'Get a cocktail/drink by ID' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs cocktail_get_by_id 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_get_by_id, this is the rule to start with:
cocktail_get_by_id 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_get_by_id call is checked against it from then on.
Questions about cocktail_get_by_id
Get a cocktail/drink by ID. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
cocktail_get_by_id accepts 1 parameter: id. Required: 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 cocktail_get_by_id: 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_get_by_id 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_get_by_id 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_get_by_id. 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_get_by_id 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