Retrieve a specific recipe by its slug identifier. Use this when to get full recipe details for tasks like updating or displaying the recipe. Args: slug: The unique text identifier for the recipe, typically found in recipe URLs or from get_recipes results. Returns: Dict[str, Any]: Comprehensive r...
AI agents call get_recipe_detailed to retrieve information from Mealie MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a straightforward data retrieval operation with no side effects. It queries an existing recipe and returns its details without creating, modifying, or deleting data. The use case mentioned ('tasks like updating or displaying the recipe') indicates display is a primary purpose. This is a classic Read operation.
From the tool's definition Tool retrieves recipe data by slug identifier and returns comprehensive recipe details (ingredients, instructions, nutrition information, notes, metadata). Description explicitly states 'Retrieve' and 'get full recipe details'.
Documented attack patterns abuse exactly the kind of access get_recipe_detailed 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 get_recipe_detailed:
{
"version": "1",
"default": "deny",
"tools": {
"get_recipe_detailed": {}
}
}get_recipe_detailed is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieve a specific recipe by its slug identifier. Use this when to get full recipe details for tasks like updating or displaying the recipe. Args: slug: The unique text identifier for the recipe, typically found in recipe URLs or from get_recipes results. Returns: Dict[str, Any]: Comprehensive recipe details including ingredients, instructions, nutrition information, notes, and associated metadata. It is categorised as a Read tool in the Mealie MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Mealie MCP Server MCP server in PolicyLayer and add a rule for get_recipe_detailed: 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.
get_recipe_detailed is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_recipe_detailed 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 get_recipe_detailed. 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.
get_recipe_detailed 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.