Patch a meal-plan entry. Only non-empty fields are sent.
AI agents use update_mealplan 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 meal-plan data reversibly. It does not delete data (ruling out Destructive), does not execute arbitrary code or external operations (ruling out Execute), and does not involve financial transactions (ruling out Financial). The operation can be undone via subsequent updates, placing it squarely in the Write category.
From the tool's definition Tool description states 'Patch a meal-plan entry', which is an update/modification operation. The 'Patch' HTTP method and 'Only non-empty fields are sent' language indicate reversible modification of existing data.
Attacks that exploit this kind of access
Patch a meal-plan entry. Only non-empty fields are sent. 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 update_mealplan: 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.
update_mealplan 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_mealplan 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_mealplan. 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_mealplan 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 →