# get_cocktail_by_tags

Find cocktails by tags.

Agent View of the PolicyLayer registry record for `get_cocktail_by_tags`. HTML page: https://policylayer.com/tools/00200200-cocktails-rag-mcp/get-cocktail-by-tags

## Facts

- Tool: `get_cocktail_by_tags`
- Server: Cocktails RAG MCP Server (`00200200/cocktails-rag-mcp`) — https://policylayer.com/tools/00200200-cocktails-rag-mcp.md
- Homepage: https://github.com/00200200/cocktails-rag-mcp
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_cocktail_by_tags",
    "arguments": {}
  }
}
```

## Why get_cocktail_by_tags is rated Low

This tool searches or filters cocktail records based on tag criteria. It retrieves information with no side effects, state changes, or external operations. The blast radius of misuse is minimal—an agent cannot cause harm by querying cocktail data.

From the tool's own definition: "Tool name 'get_cocktail_by_tags' and description 'Find cocktails by tags' indicate a retrieval operation that queries the cocktail database without modifying, executing, or deleting data."

## Use case

AI agents call get_cocktail_by_tags to retrieve information from Cocktails RAG MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Cocktails RAG MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_cocktail_by_tags": {}
  }
}
```

## Other tools on Cocktails RAG MCP Server (6)

- `ask_about_cocktail` — Read — https://policylayer.com/tools/00200200-cocktails-rag-mcp/ask-about-cocktail.md
- `get_cocktail_by_category` — Read — https://policylayer.com/tools/00200200-cocktails-rag-mcp/get-cocktail-by-category.md
- `get_cocktail_by_glass` — Read — https://policylayer.com/tools/00200200-cocktails-rag-mcp/get-cocktail-by-glass.md
- `get_cocktail_by_name` — Read — https://policylayer.com/tools/00200200-cocktails-rag-mcp/get-cocktail-by-name.md
- `suggest_cocktail` — Read — https://policylayer.com/tools/00200200-cocktails-rag-mcp/suggest-cocktail.md
- `suggest_cocktail_by_ingredients` — Read — https://policylayer.com/tools/00200200-cocktails-rag-mcp/suggest-cocktail-by-ingredients.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=00200200-cocktails-rag-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/00200200-cocktails-rag-mcp