Search food additive records by keyword, function, category, dietary filter, or health concern for additive discovery and selection. Input: food additive keyword (e.g. 'preservative', 'sweetener', 'hyperactivity', 'banned', 'E1') with optional filter (high_risk, allergens, banned, not_vegan, not_...
Risk signalsAccepts freeform code/query input (query)
Part of the Food Safety server.
Free to start. No card required.
AI agents call search_additives 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 search_additives 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": {
"search_additives": {}
}
}See the full Food Safety policy for all 5 tools.
These attack patterns abuse exactly the kind of access search_additives 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.
Search food additive records by keyword, function, category, dietary filter, or health concern for additive discovery and selection. Input: food additive keyword (e.g. 'preservative', 'sweetener', 'hyperactivity', 'banned', 'E1') with optional filter (high_risk, allergens, banned, not_vegan, not_halal). Returns: matching additive names, E-numbers, CAS numbers, Hebrew names, categories, functions, safety scores (1-10), EU/US status, health concerns, allergen flags, dietary status (vegan/halal/kosher), and ADI values. Database: 6,450+ food additives searchable by name, function, category, and Hebrew name. For food additive discovery and category exploration. Do not use when the user has an exact additive name/E-number for full safety data (use check_additive).. 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 search_additives: 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.
search_additives 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 search_additives 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 search_additives. 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.
search_additives 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.