start_execution_run

SERVERNodebench SOURCEnodebench-mcp

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-homenshum-nodebench/start-execution-run.md

WHAT IT DOES

What start_execution_run does on Nodebench

AI agents invoke start_execution_run to trigger actions in Nodebench. 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 start_execution_run is rated High

This tool initiates a live execution run with durable side effects (task session creation, trace logging). It is an Execute category tool because it triggers workflow operations whose outcomes depend on the workflow definition and arguments provided.

From the tool's definition start_execution_run" starts a live execution trace run for a workflow, creates a task session and trace, and implies triggering external operations whose effects depend on workflow arguments

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs start_execution_run safely

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

start_execution_run Rate-limited

start_execution_run 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": {
    "start_execution_run": {
      "limits": [
        {
          "counter": "start_execution_run_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 Nodebench, apply this rule, and every start_execution_run call is checked against it from then on.

FAQ

Questions about start_execution_run

What does the start_execution_run tool do? +

Start a live Convex-backed execution trace run for a workflow. Creates a task session and trace together so later steps, decisions, evidence, verifications, and approvals all land on the same durable run. It is categorised as a Execute tool in the Nodebench MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start_execution_run? +

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

What risk level is start_execution_run? +

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

Can I rate-limit start_execution_run? +

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

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

start_execution_run is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nodebench, and thousands of servers like it.

This server

All 824 Nodebench tools → High-risk tools on this server →

Across the catalogue

start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP →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 →