flow_run_now

Fire one action immediately — no flow, no enrollment, no schedule. Useful for one-shot sends (

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/flow-run-now.md

WHAT IT DOES

What flow_run_now does on 0nmcp

AI agents invoke flow_run_now 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 flow_run_now is rated High

flow_run_now triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

flow_run_now Rate-limited

flow_run_now 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": {
    "flow_run_now": {
      "limits": [
        {
          "counter": "flow_run_now_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 flow_run_now call is checked against it from then on.

FAQ

Questions about flow_run_now

What does the flow_run_now tool do? +

Fire one action immediately — no flow, no enrollment, no schedule. Useful for one-shot sends (. 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 flow_run_now? +

Register the 0n MCP server in PolicyLayer and add a rule for flow_run_now: 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 flow_run_now? +

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

Can I rate-limit flow_run_now? +

Yes. Add a rate_limit block to the flow_run_now 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 flow_run_now completely? +

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

flow_run_now 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 →