Patch a cookbook. Use public=1 to make public, public=0 to unpublish.
AI agents use update_cookbook 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 cookbook metadata (publication status) but does not delete data or execute arbitrary operations. Changes are reversible—a cookbook can be unpublished and republished. This is a standard write operation on a recipe management system with minimal blast radius, as it only affects visibility/sharing state of a single cookbook resource.
From the tool's definition Tool name 'update_cookbook' and description 'Patch a cookbook' indicate modification of existing data. The specific mention of setting public/unpublish flags shows reversible state changes to a cookbook resource.
Attacks that exploit this kind of access
Patch a cookbook. Use public=1 to make public, public=0 to unpublish. 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_cookbook: 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_cookbook 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_cookbook 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_cookbook. 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_cookbook 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 →