Merge one food into another (consolidate duplicates).
AI agents use merge_foods 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.
Merging foods modifies the food database by consolidating duplicate entries into a single record. While this is a write operation that could affect meal planning and nutritional data, it is reversible (the original food entry can be separated if needed) and does not permanently destroy data like deletion would.
From the tool's definition Tool name 'merge_foods' and description 'Merge one food into another (consolidate duplicates)' indicates modifying food data by combining records. This is a reversible write operation that consolidates data rather than deleting it.
Attacks that exploit this kind of access
Merge one food into another (consolidate duplicates). 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 merge_foods: 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.
merge_foods 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 merge_foods 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 merge_foods. 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.
merge_foods 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 →