This record as markdown: /tools/creativelead-unclick/food-search.md
What food_search does on UnClick
AI agents call food_search to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | number | — | |
query | string | — | |
page_size | number | — |
Parameters from the server's own tool schema.
Why food_search is rated Low
This tool retrieves data from Open Food Facts without creating, modifying, deleting, or executing external operations. It is a straightforward read-only search function with minimal risk if misused by an AI agent.
From the tool's definition Tool name 'food_search' combined with description 'Search for food products on Open Food Facts' indicates a query operation with no modification or side effects.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
The rule that runs food_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For food_search, this is the rule to start with:
food_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every food_search call is checked against it from then on.
Questions about food_search
Search for food products on Open Food Facts. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
food_search accepts 3 parameters: page, query, page_size. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for food_search: 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 UnClick. Nothing to install.
food_search 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 food_search 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 food_search. 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.
food_search is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue