Scan a packaged-food product ingredient list for additive safety risks, regulatory compliance, allergens, and dietary compatibility across target markets. Input: comma-separated ingredient list as printed on food packaging (up to 60 ingredients). Returns per-ingredient: matched additive name, E-n...
Part of the Food Safety server.
Free to start. No card required.
AI agents call check_ingredient_list to retrieve information from Food Safety 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 check_ingredient_list 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.
{
"version": "1",
"default": "deny",
"tools": {
"check_ingredient_list": {}
}
}See the full Food Safety policy for all 5 tools.
These attack patterns abuse exactly the kind of access check_ingredient_list gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Scan a packaged-food product ingredient list for additive safety risks, regulatory compliance, allergens, and dietary compatibility across target markets. Input: comma-separated ingredient list as printed on food packaging (up to 60 ingredients). Returns per-ingredient: matched additive name, E-number, safety score (1-10), category, EU/US status, health concerns, allergen flags, and ADI. Returns overall: LOW/MODERATE/HIGH risk assessment, average safety score, flagged high-risk additives with reasons and banned-country data, allergen warnings, and market-specific compliance notes. Database: 6,450+ food additives with 77,278 synonyms for fuzzy matching. For food product safety screening and market compliance. Do not use for single additive lookup (use check_additive), nutrition facts (use check_nutrition), or pesticide MRLs (use check_pesticide_mrl).. It is categorised as a Read tool in the Food Safety MCP Server, which means it retrieves data without modifying state.
Register the Food Safety MCP server in PolicyLayer and add a rule for check_ingredient_list: 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 Food Safety. Nothing to install.
check_ingredient_list 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 check_ingredient_list 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 check_ingredient_list. 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.
check_ingredient_list is provided by the Food Safety MCP server (https://food-mcp-server.rootsbybenda.workers.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 Food Safety 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.