Replace/update multiple recipes through Mealie's batch endpoint.
AI agents use update_many_recipes 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 falls under Write category as it modifies existing recipes without permanently deleting them. However, the 'Replace' option and batch nature affecting multiple recipes elevates severity to 'high' due to the potential blast radius if an AI misuses this to overwrite many recipes at once.
From the tool's definition Tool name 'update_many_recipes' and description 'Replace/update multiple recipes through Mealie's batch endpoint' indicate the tool modifies recipe data in bulk.
Attacks that exploit this kind of access
Replace/update multiple recipes through Mealie's batch endpoint. 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_many_recipes: 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_many_recipes 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_many_recipes 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_many_recipes. 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_many_recipes is provided by the Mealie MCP Server MCP server (nikopol666/mealie-mcp). 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 →