AI agents call analyzeProduct 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.
The tool queries the OpenFoodFacts database to retrieve nutritional information and applies AI analysis to present it; this is a read operation that retrieves data. There is no indication the tool creates, modifies, deletes, or executes arbitrary code. The low severity reflects minimal blast radius—misuse would only surface incorrect nutritional analysis, not compromise data integrity or trigger unintended actions.
From the tool's definition Tool description states 'Get AI nutritional analysis of a product' — retrieves and analyzes existing product data without modification, deletion, or execution of external operations. No side effects are described.
Documented attack patterns abuse exactly the kind of access analyzeProduct 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 analyzeProduct:
{
"version": "1",
"default": "deny",
"tools": {
"analyzeProduct": {}
}
} analyzeProduct 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.
Get AI nutritional analysis of a product. 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 analyzeProduct: 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.
analyzeProduct 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 analyzeProduct 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 analyzeProduct. 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.
analyzeProduct 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.