set_recipe_instructions
AI agents use set_recipe_instructions to create or update resources in Mcp Mealie — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Mealie environment.
This tool modifies recipe instructions, which is a data write operation. It is reversible (instructions can be updated or deleted later), so it falls under Write rather than Destructive. The blast radius is medium because incorrect instructions could affect meal planning and food preparation, but the data can be corrected.
From the tool's definition Tool name 'set_recipe_instructions' indicates modification of recipe data. Server context shows this is part of Mealie's recipe management API. The action of 'set' implies creating or updating recipe instructions, which is reversible.
Attacks that exploit this kind of access
set_recipe_instructions. It is categorised as a Write tool in the Mcp Mealie MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Mealie MCP server in PolicyLayer and add a rule for set_recipe_instructions: 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 Mcp Mealie. Nothing to install.
set_recipe_instructions 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 set_recipe_instructions 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 set_recipe_instructions. 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.
set_recipe_instructions is provided by the Mcp Mealie MCP server (obrien-matthew/mcp-mealie). 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 →