trigger_recipe_action

What trigger_recipe_action does on Mealie MCP Server

AI agents invoke trigger_recipe_action to trigger actions in Mealie MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why trigger_recipe_action is rated High

This tool executes an action on a recipe object. Without knowing the specific range of actions available, the ability to 'trigger' actions represents execution capability that could have side effects beyond simple CRUD operations. While not destructive by nature, it goes beyond Read (retrieval) and Write (creation/modification), as it invokes operations whose outcomes depend on the argument passed.

From the tool's definition The tool description states 'Trigger one household recipe action for a recipe slug.' The term 'trigger' combined with 'action' indicates the tool executes or initiates some operation on a recipe, the effects of which depend on what action is being triggered.

The rule that runs trigger_recipe_action 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 trigger_recipe_action, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "trigger_recipe_action": {
      "limits": [
        {
          "counter": "trigger_recipe_action_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about trigger_recipe_action