Make a direct call to any Open Food Facts API endpoint. Use get_api_docs to see available endpoints. Auth credentials are included automatically for write operations if configured. Two body modes for writes: - params: form-encoded (for /cgi/*.pl and /api/v2/* legacy endpoints) - json_body: raw JS...
AI agents invoke call_api to trigger actions in Open Food Facts. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool can issue any HTTP method (GET, POST, PATCH, DELETE, etc.) to any API endpoint, making it a general-purpose executor. It spans Read, Write, and potentially Destructive categories depending on what endpoint and method is invoked. Per the rules, Execute is chosen as it runs arbitrary API operations whose effects depend entirely on the arguments.
From the tool's definition 'Make a direct call to any Open Food Facts API endpoint' and 'Auth credentials are included automatically for write operations if configured' — arbitrary endpoint calls with any HTTP method including destructive operations
Attacks that exploit this kind of access
Make a direct call to any Open Food Facts API endpoint. Use get_api_docs to see available endpoints. Auth credentials are included automatically for write operations if configured. Two body modes for writes: - params: form-encoded (for /cgi/*.pl and /api/v2/* legacy endpoints) - json_body: raw JSON (for /api/v3/* endpoints — required for structured fields like packagings) Example v3 packagings write: method: PATCH endpoint: /api/v3/product/0123456789012 json_body: {. It is categorised as a Execute tool in the Open Food Facts MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Open Food Facts MCP server in PolicyLayer and add a rule for call_api: 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 Open Food Facts. Nothing to install.
call_api is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the call_api 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 call_api. 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.
call_api is provided by the Open Food Facts MCP server (openfoodfacts-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →