openbeautyfacts.product.search
Search cosmetics/personal-care products by name — returns matching products with brand, barcode, categories, image. Shampoo, lipstick, sunscreen, and more (Open Beauty Facts)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/openbeautyfacts.product.search.md
What openbeautyfacts.product.search does on Apibase
AI agents call openbeautyfacts.product.search to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Results count (default 10, max 50) |
query | string | Yes | Cosmetics/personal-care product name to search (e.g. "shampoo", "lipstick", "sunscreen") |
Parameters from the server's own tool schema.
Why openbeautyfacts.product.search is rated Low
Tool retrieves product data without modification, deletion, or execution effects.
From the tool's definition Search cosmetics/personal-care products by name — returns matching products
Attacks that exploit this kind of access
The rule that runs openbeautyfacts.product.search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For openbeautyfacts.product.search, this is the rule to start with:
openbeautyfacts.product.search 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 Apibase, apply this rule, and every openbeautyfacts.product.search call is checked against it from then on.
Questions about openbeautyfacts.product.search
Search cosmetics/personal-care products by name — returns matching products with brand, barcode, categories, image. Shampoo, lipstick, sunscreen, and more (Open Beauty Facts). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
openbeautyfacts.product.search accepts 2 parameters: limit, query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for openbeautyfacts.product.search: 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 Apibase. Nothing to install.
openbeautyfacts.product.search 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 openbeautyfacts.product.search 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 openbeautyfacts.product.search. 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.
openbeautyfacts.product.search is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue