Check if a product contains any of multiple allergens at once
AI agents call checkMultipleAllergens 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 retrieves and queries allergen information from the OpenFoodFacts database to provide safety information to users. It has no side effects, cannot modify or delete data, does not execute arbitrary code, and poses no financial risk. It is a straightforward read operation with low blast radius if misused—worst case being incorrect allergen information returned, which does not alter system state.
From the tool's definition Tool is named 'checkMultipleAllergens' and described as checking if a product contains allergens. The verb 'check' and the passive query nature (no modification of data) indicate a read-only operation.
Documented attack patterns abuse exactly the kind of access checkMultipleAllergens 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 checkMultipleAllergens:
{
"version": "1",
"default": "deny",
"tools": {
"checkMultipleAllergens": {}
}
}checkMultipleAllergens 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 any of multiple allergens at once. 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 checkMultipleAllergens: 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.
checkMultipleAllergens 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 checkMultipleAllergens 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 checkMultipleAllergens. 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.
checkMultipleAllergens 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.