Use this tool when the user doesn't know the exact INCI name and wants to discover cosmetic ingredients by partial name, function (e.g. 'sunscreen', 'emulsifier', 'preservative', 'surfactant'), or category (e.g. 'humectant', 'UV filter', 'antioxidant'). Returns up to 20 matches per query with INC...
Accepts freeform code/query input (query)
Part of the Cosmetic Regulatory Intelligence MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call search_ingredients to retrieve information from Cosmetic Regulatory Intelligence without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though search_ingredients only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
search_ingredients:
rules:
- action: allowSee the full Cosmetic Regulatory Intelligence policy for all 4 tools.
Agents calling read-class tools like search_ingredients have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Use this tool when the user doesn't know the exact INCI name and wants to discover cosmetic ingredients by partial name, function (e.g. 'sunscreen', 'emulsifier', 'preservative', 'surfactant'), or category (e.g. 'humectant', 'UV filter', 'antioxidant'). Returns up to 20 matches per query with INCI name, CAS number, functional category, safety rating, EU status, and concern level. Fast discovery tool — best for identifying candidate ingredients before deep-diving with check_ingredient. Do not use for known INCI lookups (use check_ingredient directly); do not use for batch compliance (use check_formula).. It is categorised as a Read tool in the Cosmetic Regulatory Intelligence MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for search_ingredients. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Cosmetic Regulatory Intelligence MCP server.
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 Intercept 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 Intercept 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 Cosmetic Regulatory Intelligence MCP server (twohalves/cosmetic-regulatory). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept