Replaces the ingredients and instructions of an existing recipe. PREFERRED: Use structured ingredients with {quantity, unit, food, note} for proper tracking in Mealie. This enables meal planning and shopping list features. Plain text strings are supported as fallback but lose these benefits. When...
AI agents use update_recipe to create or update resources in Mealie MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mealie MCP Server environment.
This tool modifies (updates) recipe data in the Mealie database. It is reversible because recipes can be edited again or restored, distinguishing it from deletion (Destructive). The blast radius is moderate: incorrect recipe modifications could affect meal plans or shopping lists derived from that recipe, but the impact is limited to recipe metadata and is not permanent.
From the tool's definition The tool description states it 'Replaces the ingredients and instructions of an existing recipe' — a modification operation that alters existing data reversibly.
Attacks that exploit this kind of access
Replaces the ingredients and instructions of an existing recipe. PREFERRED: Use structured ingredients with {quantity, unit, food, note} for proper tracking in Mealie. This enables meal planning and shopping list features. Plain text strings are supported as fallback but lose these benefits. When using structured ingredients with a food name that doesn. It is categorised as a Write tool in the Mealie MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mealie MCP Server MCP server in PolicyLayer and add a rule for update_recipe: 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 Mealie MCP Server. Nothing to install.
update_recipe is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_recipe 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 update_recipe. 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.
update_recipe is provided by the Mealie MCP Server MCP server (that0n3guy/mealie-mcp-server-ts). 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 →