Search for ingredients in the SommelierX database. Returns ingredient names, IDs, and groups. Use this to discover available ingredients before using pair_wine_with_ingredients. Best for:
AI agents call search_ingredients to retrieve information from SommelierX Wine Pairing MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a database and returns ingredient metadata (names, IDs, groups). It has no side effects, performs no modifications to data, executes no external operations, and creates no financial obligations. It is purely a read operation for discovery purposes.
From the tool's definition 'Search for ingredients in the SommelierX database. Returns ingredient names, IDs, and groups.' - performs a query operation that retrieves data without modification, creation, or deletion.
Attacks that exploit this kind of access
Search for ingredients in the SommelierX database. Returns ingredient names, IDs, and groups. Use this to discover available ingredients before using pair_wine_with_ingredients. Best for:. It is categorised as a Read tool in the SommelierX Wine Pairing MCP MCP Server, which means it retrieves data without modifying state.
Register the SommelierX Wine Pairing 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 SommelierX Wine Pairing MCP. 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 SommelierX Wine Pairing MCP server (rogertheunissenmerge-oss/mcp-server). 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 →