Search Open Food Facts using the Search-a-licious Elasticsearch backend. Powered by Lucene query syntax with full boolean logic and negation support. Use this instead of search_products_standard when you need: - Negation queries: find gluten-free cereals with allergens_tags_without=
AI agents call search_products_lucene to retrieve information from Open Food Facts without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data from the Open Food Facts database without modifying, deleting, or executing arbitrary operations. It is a read-only search operation that returns filtered product information based on Lucene query syntax. No data is created, modified, deleted, or financial transactions are initiated.
From the tool's definition Tool name contains 'search' and description states it is used to 'Search Open Food Facts using the Search-a-licious Elasticsearch backend.' The functionality is purely querying/retrieving data with 'full boolean logic and negation support' for filtering…
Attacks that exploit this kind of access
Search Open Food Facts using the Search-a-licious Elasticsearch backend. Powered by Lucene query syntax with full boolean logic and negation support. Use this instead of search_products_standard when you need: - Negation queries: find gluten-free cereals with allergens_tags_without=. It is categorised as a Read tool in the Open Food Facts MCP Server, which means it retrieves data without modifying state.
Register the Open Food Facts MCP server in PolicyLayer and add a rule for search_products_lucene: 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 Open Food Facts. Nothing to install.
search_products_lucene 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_products_lucene 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_products_lucene. 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_products_lucene is provided by the Open Food Facts MCP server (openfoodfacts-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 →