AI agents call meal_get_by_id to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes |
Parameters from the server's own tool schema.
This tool queries and retrieves meal or recipe data based on an ID parameter. It performs a simple lookup operation without creating, modifying, deleting, or executing any code. No financial, destructive, or write operations are involved. The blast radius of misuse is minimal—an agent could retrieve meal data but cannot cause harm through retrieval alone.
From the tool's definition Tool name 'meal_get_by_id' and description 'Get a meal/recipe by ID' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get a meal/recipe by ID. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
meal_get_by_id accepts 1 parameter: id. Required: id. 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_get_by_id: 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_get_by_id 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_get_by_id 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_get_by_id. 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_get_by_id is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →