run_workflow

Execute a pre-defined .0n workflow file. Workflows are deterministic, step-by-step automations stored in ~/.0n/workflows/. Unlike the

SERVER0nmcp SOURCE0nmcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-0nork-0nmcp/run-workflow.md

WHAT IT DOES

What run_workflow does on 0nmcp

AI agents invoke run_workflow to trigger actions in 0nmcp. 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.

RISK

Why run_workflow is rated High

This is an Execute-category tool because it triggers the execution of workflow automation logic. While the workflows are pre-defined (reducing some risk vs arbitrary code execution), the tool still runs complex multi-step operations whose actual impact depends on what those workflows do.

From the tool's definition Tool executes a pre-defined workflow file ('Execute a pre-defined .0n workflow file'). Workflows are described as 'step-by-step automations' that run deterministically.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_workflow safely

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

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.

The button opens the PolicyLayer dashboard: create your workspace, connect 0nmcp, apply this rule, and every run_workflow call is checked against it from then on.

FAQ

Questions about run_workflow

What does the run_workflow tool do? +

Execute a pre-defined .0n workflow file. Workflows are deterministic, step-by-step automations stored in ~/.0n/workflows/. Unlike the. It is categorised as a Execute tool in the 0nmcp 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 0n 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 0nmcp. 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 0n MCP server (0nmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 0n, and thousands of servers like it.

This server

All 218 0n tools → High-risk tools on this server →

Across the catalogue

run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →