execute-workflow

What execute-workflow does on Ruflo

AI agents invoke execute-workflow to trigger actions in Ruflo. 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 execute-workflow is rated High

This is an Execute category tool because it triggers workflow execution whose side effects are dependent on workflow parameters and cannot be fully predicted without knowing the workflow contents. The high severity reflects that a malicious agent could use this to execute arbitrary workflows within the swarm system, potentially affecting multiple agents, data processing, and external integrations.

From the tool's definition Tool name 'execute-workflow' combined with description 'Execute a workflow' indicates the tool runs automated workflows whose effects depend on the workflow definition and arguments provided.

The rule that runs execute-workflow safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ruflo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For execute-workflow, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute-workflow": {
      "limits": [
        {
          "counter": "execute-workflow_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about execute-workflow