Get Open Food Facts API documentation. Useful for understanding available endpoints before using call_api.
AI agents call get_api_docs to retrieve information from Open Food Facts without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves API documentation, which is a read-only operation that queries reference information. It produces no side effects, creates no data modifications, executes no external operations, and poses minimal risk. The documentation is typically public and intended for developers to understand available endpoints.
From the tool's definition Tool name 'get_api_docs' and description 'Get Open Food Facts API documentation' indicate retrieval of informational/reference material with no side effects or data modification.
Attacks that exploit this kind of access
Get Open Food Facts API documentation. Useful for understanding available endpoints before using call_api. It is categorised as a Read tool in the Open Food Facts MCP Server, which means it retrieves data without modifying state.
Register the Open Food Facts MCP server in PolicyLayer and add a rule for get_api_docs: 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.
get_api_docs 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 get_api_docs 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 get_api_docs. 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.
get_api_docs 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 →