This record as markdown: /tools/creativelead-unclick/meal-categories.md
What meal_categories does on UnClick
AI agents call meal_categories 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.
Why meal_categories is rated Low
This tool performs a simple read operation that queries and returns a list of meal categories. It has no side effects, does not modify data, and does not execute code or trigger external operations. The blast radius of misuse is minimal—an agent could only retrieve categorical information that is typically public.
From the tool's definition Tool name 'meal_categories' and description 'List all meal categories' indicate a retrieval operation that returns meal category data without modification or execution of external code.
Attacks that exploit this kind of access
The rule that runs meal_categories 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_categories, this is the rule to start with:
meal_categories 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_categories call is checked against it from then on.
Questions about meal_categories
List all meal categories. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
Register the UnClick MCP server in PolicyLayer and add a rule for meal_categories: 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_categories 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_categories 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_categories. 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_categories 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