Search for ingredients by name to find their IDs
AI agents call search_ingredients to retrieve information from Bar Assistant MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about ingredients without creating, modifying, deleting, or executing any operations. It is a simple lookup function that returns ingredient identifiers based on search criteria. No data is written, destroyed, or executed; the operation is read-only with minimal blast radius if misused.
From the tool's definition Tool description states 'Search for ingredients by name to find their IDs' - a pure query operation with no side effects. The verb 'search' and the stated purpose of finding/retrieving ingredient IDs indicates data retrieval only.
Attacks that exploit this kind of access
Search for ingredients by name to find their IDs. It is categorised as a Read tool in the Bar Assistant MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bar Assistant MCP Server MCP server in PolicyLayer and add a rule for search_ingredients: 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 Bar Assistant MCP Server. Nothing to install.
search_ingredients 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 search_ingredients 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 search_ingredients. 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.
search_ingredients is provided by the Bar Assistant MCP Server MCP server (the-real-py/bar-assistant-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →