Update an existing recipe
AI agents use update_recipe to create or update resources in Saffron MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Saffron MCP Server environment.
This tool modifies existing recipe data reversibly. It is a Write operation because updates can be undone (recipes can be re-updated to previous values, deleted, or restored from backups in typical recipe management systems). While it affects data, it does not irreversibly delete content (Destructive), execute arbitrary commands (Execute), or move money (Financial).
From the tool's definition Tool name 'update_recipe' combined with description 'Update an existing recipe' indicates modification of existing data. The server description mentions 'creating and updating recipes' as core functionality.
Attacks that exploit this kind of access
Update an existing recipe. It is categorised as a Write tool in the Saffron MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Saffron MCP Server MCP server in PolicyLayer and add a rule for update_recipe: 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 Saffron MCP Server. Nothing to install.
update_recipe 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_recipe 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_recipe. 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_recipe is provided by the Saffron MCP Server MCP server (tvh/saffron-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 →