Low Risk

off_get_product

Fetch a packaged food product by barcode (EAN-13 or UPC) from Open Food Facts. Returns the product name, brand, quantity, ingredients (raw text and parsed list), allergens, additives, computed scores (Nutri-Score a–e, NOVA 1–4, Green-Score), nutrition per 100g and per serving, categories, labels,...

Part of the Openfoodfacts Mcp Server server.

off_get_product is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE OPENFOODFACTS MCP SERVER →

Free to start. No card required.

AI agents call off_get_product to retrieve information from Openfoodfacts Mcp Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though off_get_product only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "off_get_product": {}
  }
}

See the full Openfoodfacts Mcp Server policy for all 4 tools.

Get this rule live on your own Openfoodfacts Mcp Server server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY OPENFOODFACTS MCP SERVER →

These attack patterns abuse exactly the kind of access off_get_product gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so off_get_product only ever does what you allow.

SECURE OPENFOODFACTS MCP SERVER →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the off_get_product tool do? +

Fetch a packaged food product by barcode (EAN-13 or UPC) from Open Food Facts. Returns the product name, brand, quantity, ingredients (raw text and parsed list), allergens, additives, computed scores (Nutri-Score a–e, NOVA 1–4, Green-Score), nutrition per 100g and per serving, categories, labels, packaging, origins, image URL, and data completeness. Open Food Facts is a crowd-sourced database — a missing field means "not yet entered by contributors," not that the attribute is absent from the actual product. Computed scores carry regional formula caveats and are indicators, not absolute rankings. Data is under ODbL 1.0 — cite Open Food Facts in downstream use.. It is categorised as a Read tool in the Openfoodfacts Mcp Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on off_get_product? +

Register the Openfoodfacts Mcp Server MCP server in PolicyLayer and add a rule for off_get_product: 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 Server. Nothing to install.

What risk level is off_get_product? +

off_get_product is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit off_get_product? +

Yes. Add a rate_limit block to the off_get_product 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.

How do I block off_get_product completely? +

Set action: deny in the PolicyLayer policy for off_get_product. 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.

What MCP server provides off_get_product? +

off_get_product is provided by the Openfoodfacts Mcp Server MCP server (@cyanheads/openfoodfacts-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Openfoodfacts Mcp Server tool call.

Deterministic rules across all 4 Openfoodfacts Mcp Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.