food.product.barcode

Lookup food product by barcode (EAN/UPC) — name, brand, nutrition (calories, fat, carbs, protein per 100g), Nutri-Score, NOVA group, ingredients. 3M+ products (Open Food Facts)

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/food.product.barcode.md

WHAT IT DOES

What food.product.barcode does on Apibase

AI agents call food.product.barcode to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`barcode`	string	Yes	Product barcode (EAN-13, UPC-A, etc.) e.g. "3017620422003" for Nutella

Parameters from the server's own tool schema.

RISK

Why food.product.barcode is rated Low

Retrieves publicly available food product data with no side effects or modifications.

From the tool's definition Lookup food product by barcode — name, brand, nutrition, ingredients.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs food.product.barcode safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For food.product.barcode, this is the rule to start with:

food.product.barcode Allowed

food.product.barcode is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "food.product.barcode": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every food.product.barcode call is checked against it from then on.

FAQ

Questions about food.product.barcode

What does the food.product.barcode tool do? +

Lookup food product by barcode (EAN/UPC) — name, brand, nutrition (calories, fat, carbs, protein per 100g), Nutri-Score, NOVA group, ingredients. 3M+ products (Open Food Facts). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does food.product.barcode accept? +

food.product.barcode accepts 1 parameter: barcode. Required: barcode. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on food.product.barcode? +

Register the Apibase MCP server in PolicyLayer and add a rule for food.product.barcode: 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 Apibase. Nothing to install.

What risk level is food.product.barcode? +

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

Can I rate-limit food.product.barcode? +

Yes. Add a rate_limit block to the food.product.barcode 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 food.product.barcode completely? +

Set action: deny in the PolicyLayer policy for food.product.barcode. 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 food.product.barcode? +

food.product.barcode is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →