Partially update a recipe (only updates provided fields). Args: slug: The unique text identifier for the recipe to be updated. name: New name for the recipe (optional) description: New description for the recipe (optional) recipe_yield: New yield/servings for the recipe (optional) total_time: New...
AI agents use patch_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.
The patch_recipe tool modifies existing recipe data but does not delete or destroy information, nor does it execute arbitrary code or move financial resources. Updates are reversible—previous recipe versions can be restored. The blast radius is limited to recipe metadata within a meal planning application, affecting only the specific recipe identified by slug.
From the tool's definition Tool performs partial update of recipe data with optional fields (name, description, recipe_yield, total_time). Description explicitly states 'Partially update a recipe (only updates provided fields).' This is a reversible modification operation.
Documented attack patterns abuse exactly the kind of access patch_recipe gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mealie MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for patch_recipe:
{
"version": "1",
"default": "deny",
"tools": {
"patch_recipe": {
"limits": [
{
"counter": "patch_recipe_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}patch_recipe stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Partially update a recipe (only updates provided fields). Args: slug: The unique text identifier for the recipe to be updated. name: New name for the recipe (optional) description: New description for the recipe (optional) recipe_yield: New yield/servings for the recipe (optional) total_time: New total time for the recipe (optional) Returns: Dict[str, Any]: The updated recipe details. 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 patch_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.
patch_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 patch_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 patch_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.
patch_recipe is provided by the Mealie MCP Server MCP server (rldiao/mealie-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 44 Mealie MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
44 Mealie MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.