create_shared_recipe_record
Create a shared recipe record using a Mealie-native payload.
This record as markdown: /tools/nikopol666-mealie-mcp/create-shared-recipe-record.md
What create_shared_recipe_record does on Mealie MCP Server
AI agents use create_shared_recipe_record 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.
Why create_shared_recipe_record is rated Medium
This tool creates new data (a shared recipe record) but does not execute arbitrary code, delete data irreversibly, or move financial assets. Creation is reversible through deletion or modification, making it a Write-category risk. Severity is medium because creating shared records could expose data to unintended audiences or pollute the recipe database if misused by an agent, but the impact is recoverable.
From the tool's definition Tool name 'create_shared_recipe_record' and description 'Create a shared recipe record' indicate creation of a new data record. The verb 'create' and the action of establishing a new shared recipe constitutes a reversible write operation.
Attacks that exploit this kind of access
The rule that runs create_shared_recipe_record safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mealie MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_shared_recipe_record, this is the rule to start with:
create_shared_recipe_record stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mealie MCP Server, apply this rule, and every create_shared_recipe_record call is checked against it from then on.
Questions about create_shared_recipe_record
Create a shared recipe record using a Mealie-native payload. 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 create_shared_recipe_record: 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.
create_shared_recipe_record 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_shared_recipe_record 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_shared_recipe_record. 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_shared_recipe_record 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.
More on Mealie MCP Server, and thousands of servers like it.
This server
Across the catalogue