Upload a product image to Open Food Facts. Requires OFF_USER_ID and OFF_PASSWORD.\n\nPrefer more photos over fewer. Panels with text (ingredients, nutrition, certifications, recycling instructions) are highest value as OFF can OCR them. Plain sides with just a colour or logo are lowest value but ...
AI agents use upload_image to create or update resources in Open Food Facts — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Open Food Facts environment.
This tool creates new data (product images) in the Open Food Facts database, which is a reversible Write operation. It does not delete, destroy, or execute arbitrary code. The medium severity reflects that while image uploads can be reversed/deleted, malicious actors could flood the database with low-quality or inappropriate images, impacting data quality and requiring manual cleanup.
From the tool's definition Tool description states 'Upload a product image to Open Food Facts' and requires authentication (OFF_USER_ID and OFF_PASSWORD). The function creates/adds new image data to the database.
Attacks that exploit this kind of access
Upload a product image to Open Food Facts. Requires OFF_USER_ID and OFF_PASSWORD.\n\nPrefer more photos over fewer. Panels with text (ingredients, nutrition, certifications, recycling instructions) are highest value as OFF can OCR them. Plain sides with just a colour or logo are lowest value but still worth uploading if you have them.\n\nUse the most appropriate imagefield (front, ingredients, nutrition, packaging). Use. It is categorised as a Write tool in the Open Food Facts MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Open Food Facts MCP server in PolicyLayer and add a rule for upload_image: 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.
upload_image is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the upload_image 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 upload_image. 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.
upload_image 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 →