AI agents use create_recipe to create or update resources in Paprika — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Paprika environment.
This tool creates new recipe data in the Paprika system, which is a reversible Write operation (recipes can be deleted or modified). While it incurs a small financial cost (~$0.002 per auto-generated image), the primary function is data creation, not financial commitment—the cost is a secondary effect of the optional image generation feature.
From the tool's definition Tool description states 'Create a new recipe in Paprika' and mentions auto-generating images via external API (Replicate). The name 'create_recipe' and description explicitly indicate data creation with reversible side effects.
Attacks that exploit this kind of access
Create a new recipe in Paprika. Auto-generates professional AI food photography (~$0.002 per image using Replicate). Set generate_image=false to disable. It is categorised as a Write tool in the Paprika MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Paprika MCP server in PolicyLayer and add a rule for create_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 Paprika. Nothing to install.
create_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 create_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 create_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.
create_recipe is provided by the Paprika MCP server (sandordaroczi/paprika-mcp-python-server). 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 →