Get the Eco-Score (environmental impact rating A-E) for a product
AI agents call getEcoScore 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 is a straightforward read operation that fetches and returns environmental impact rating information for a food product. It has no side effects, does not modify data, execute code, delete anything, or involve financial transactions. The low severity reflects minimal risk even if misused by an AI agent, as it only exposes read-only food data.
From the tool's definition Tool name is 'getEcoScore' and description states 'Get the Eco-Score (environmental impact rating A-E) for a product' — a retrieval operation that queries existing data from the OpenFoodFacts database with no modification, deletion, or execution of external…
Documented attack patterns abuse exactly the kind of access getEcoScore 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 getEcoScore:
{
"version": "1",
"default": "deny",
"tools": {
"getEcoScore": {}
}
} getEcoScore 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 the Eco-Score (environmental impact rating A-E) for 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 getEcoScore: 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.
getEcoScore 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 getEcoScore 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 getEcoScore. 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.
getEcoScore 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.