get_cocktail_by_category
Find cocktails by category.
This record as markdown: /tools/00200200-cocktails-rag-mcp/get-cocktail-by-category.md
What get_cocktail_by_category does on Cocktails RAG MCP Server
AI agents call get_cocktail_by_category 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.
Why get_cocktail_by_category is rated Low
This tool retrieves or queries cocktail data based on category filters. It has no side effects, does not modify data, execute code, delete records, or involve financial transactions. It is a straightforward read operation consistent with the server's purpose as a cocktail information retrieval system.
From the tool's definition Tool name 'get_cocktail_by_category' and description 'Find cocktails by category' indicate a retrieval operation.
Attacks that exploit this kind of access
The rule that runs get_cocktail_by_category safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cocktails RAG MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_cocktail_by_category, this is the rule to start with:
get_cocktail_by_category 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 Cocktails RAG MCP Server, apply this rule, and every get_cocktail_by_category call is checked against it from then on.
Questions about get_cocktail_by_category
Find cocktails by category. It is categorised as a Read tool in the Cocktails RAG MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cocktails RAG MCP Server MCP server in PolicyLayer and add a rule for get_cocktail_by_category: 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 Cocktails RAG MCP Server. Nothing to install.
get_cocktail_by_category 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 get_cocktail_by_category 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 get_cocktail_by_category. 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.
get_cocktail_by_category is provided by the Cocktails RAG MCP Server MCP server (00200200/cocktails-rag-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cocktails RAG MCP Server, and thousands of servers like it.
This server
Across the catalogue