request_execution_approval

Request a human approval gate for a risky execution-trace action. Approval state is written onto the live run so the UI and ledger can show the pending handoff.

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/request-execution-approval.md

WHAT IT DOES

What request_execution_approval does on Nodebench

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

The tool is classified as Execute rather than Write because it governs the execution and approval of risky actions on a live run, which is a runtime operation control mechanism. While it does write state, the primary function is managing the execution lifecycle of potentially dangerous operations. The severity is high because misconfiguring approval gates could allow unauthorized or dangerous executions to proceed.

From the tool's definition The tool name and description indicate it handles 'risky execution-trace action' and writes 'approval state is written onto the live run.' This is fundamentally an execution control mechanism that interacts with live runtime operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

request_execution_approval Rate-limited

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

FAQ

Questions about request_execution_approval

What does the request_execution_approval tool do? +

Request a human approval gate for a risky execution-trace action. Approval state is written onto the live run so the UI and ledger can show the pending handoff. 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 request_execution_approval? +

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

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

Can I rate-limit request_execution_approval? +

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

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

request_execution_approval 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

request_elevation on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

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