complete_execution_run

Finish a live execution run by updating session status, trace status, and optional usage metrics. Use this after the workflow either completes or fails.

SERVERNodebench SOURCEnodebench-mcp

Medium RISK CLASS

Category Write

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/complete-execution-run.md

WHAT IT DOES

What complete_execution_run does on Nodebench

AI agents use complete_execution_run to create or update resources in Nodebench, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nodebench environment.

RISK

Why complete_execution_run is rated Medium

This tool modifies execution metadata (session status, trace status, usage metrics) but does not delete data, execute arbitrary code, move funds, or trigger external operations with unpredictable effects. It is a state update operation on workflow execution records, making it a Write-category tool.

From the tool's definition Tool name 'complete_execution_run' and description states it 'updates session status, trace status, and optional usage metrics' - these are state modifications that change tracking/execution records.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

complete_execution_run Rate-limited

complete_execution_run stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "complete_execution_run": {
      "limits": [
        {
          "counter": "complete_execution_run_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about complete_execution_run

What does the complete_execution_run tool do? +

Finish a live execution run by updating session status, trace status, and optional usage metrics. Use this after the workflow either completes or fails. It is categorised as a Write tool in the Nodebench MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on complete_execution_run? +

Register the Nodebench MCP server in PolicyLayer and add a rule for complete_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 complete_execution_run? +

complete_execution_run is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit complete_execution_run? +

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

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

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

Across the catalogue

reminders_complete on Apple Apps MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →