run_workflow · Qontinui MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_workflow does on Qontinui MCP Server

AI agents invoke run_workflow to trigger actions in Qontinui 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 IT NEEDS A POLICY

Why run_workflow needs a policy

This tool triggers execution of visual automation workflows whose effects depend on the workflow argument/configuration. Visual automation workflows can perform arbitrary UI interactions, system commands, or external operations based on their definition.

From the tool's definition Tool name 'run_workflow' combined with description 'Run a workflow by name from the currently loaded configuration' and server description stating it 'execute[s] visual automation workflows'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_workflow Rate-limited

run_workflow stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Qontinui MCP Server, so you can run agents against it safely.

FAQ

Questions about run_workflow

What does the run_workflow tool do? +

Run a workflow by name from the currently loaded configuration. It is categorised as a Execute tool in the Qontinui MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_workflow? +

Register the Qontinui MCP Server MCP server in PolicyLayer and add a rule for run_workflow: 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 Qontinui MCP Server. Nothing to install.

What risk level is run_workflow? +

run_workflow is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_workflow? +

Yes. Add a rate_limit block to the run_workflow 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.

How do I block run_workflow completely? +

Set action: deny in the PolicyLayer policy for run_workflow. 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.

What MCP server provides run_workflow? +

run_workflow is provided by the Qontinui MCP Server MCP server (qontinui/qontinui-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.