Upload an asset file (document, PDF, etc.) for a recipe. Args: slug: The unique text identifier for the recipe. asset_path: Local file path to the asset to upload. Returns: Dict[str, Any]: Details of the uploaded asset.
AI agents use upload_recipe_asset_file 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.
This is a Write operation: it uploads files and creates new asset records associated with a recipe. While upload operations can have side effects (disk space consumption, potential security concerns if files are not validated), the operation itself is reversible (assets can typically be deleted).
From the tool's definition The tool uploads and stores files as recipe assets—'Upload an asset file (document, PDF, etc.) for a recipe.' This creates and adds data to the Mealie database reversibly.
Documented attack patterns abuse exactly the kind of access upload_recipe_asset_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mealie MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for upload_recipe_asset_file:
{
"version": "1",
"default": "deny",
"tools": {
"upload_recipe_asset_file": {
"limits": [
{
"counter": "upload_recipe_asset_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}upload_recipe_asset_file 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.
Free to start. No card required.
Upload an asset file (document, PDF, etc.) for a recipe. Args: slug: The unique text identifier for the recipe. asset_path: Local file path to the asset to upload. Returns: Dict[str, Any]: Details of the uploaded asset. 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 upload_recipe_asset_file: 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.
upload_recipe_asset_file 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 upload_recipe_asset_file 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 upload_recipe_asset_file. 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.
upload_recipe_asset_file is provided by the Mealie MCP Server MCP server (rldiao/mealie-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 44 Mealie MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
44 Mealie MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.