Check if a product contains a specific allergen (gluten, milk, eggs, nuts, peanuts, soy, fish, shellfish, etc.)
AI agents call getAllergenCheck to retrieve information from OpenFoodFacts-mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a straightforward data retrieval operation: checking allergen status for a product. It has no side effects, does not create, modify, or delete data, and does not execute code or trigger financial transactions. The risk is low because misuse would only involve querying allergen information, which could at worst provide incorrect allergen warnings but poses no destructive or operational threat.
From the tool's definition Tool name 'getAllergenCheck' and description states it 'Check if a product contains a specific allergen' — this is a query operation that retrieves allergen information from the OpenFoodFacts database without modifying data or triggering external actions.
Documented attack patterns abuse exactly the kind of access getAllergenCheck gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenFoodFacts-mcp, and nothing reaches the server without passing your rules. This is the rule we recommend for getAllergenCheck:
{
"version": "1",
"default": "deny",
"tools": {
"getAllergenCheck": {}
}
}getAllergenCheck is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check if a product contains a specific allergen (gluten, milk, eggs, nuts, peanuts, soy, fish, shellfish, etc.). It is categorised as a Read tool in the OpenFoodFacts-mcp MCP Server, which means it retrieves data without modifying state.
Register the OpenFoodFacts- MCP server in PolicyLayer and add a rule for getAllergenCheck: 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 OpenFoodFacts-mcp. Nothing to install.
getAllergenCheck 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 getAllergenCheck 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 getAllergenCheck. 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.
getAllergenCheck is provided by the OpenFoodFacts- MCP server (jagjeevanak/openfoodfacts-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OpenFoodFacts-mcp, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 OpenFoodFacts-mcp tools catalogued and risk-classified — across an index of 43,000+ MCP servers.