This record as markdown: /tools/creativelead-unclick/meal-search.md
What meal_search does on UnClick
AI agents call meal_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 |
|---|---|---|---|
query | string | — |
Parameters from the server's own tool schema.
Why meal_search is rated Low
This tool retrieves meal or recipe information based on search criteria. It is a read-only operation that queries data without modifying, executing external commands, deleting anything, or creating financial obligations. The search functionality returns information to the user with no reversible or irreversible changes to any system state.
From the tool's definition Tool name 'meal_search' and description 'Search for meals/recipes by name' indicates a query operation with no side effects.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
The rule that runs meal_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 meal_search, this is the rule to start with:
meal_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 meal_search call is checked against it from then on.
Questions about meal_search
Search for meals/recipes by name. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
meal_search accepts 1 parameter: query. 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 meal_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.
meal_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 meal_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 meal_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.
meal_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