call_driver_tool

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/call-driver-tool.md

WHAT IT DOES

What call_driver_tool does on Nodebench

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

This tool acts as a proxy to execute arbitrary operations on external MCP servers including browser automation (playwright-mcp) and mobile device control (mobile-mcp). The effects depend entirely on which driver tools are invoked through it, making it a clear Execute category tool.

From the tool's definition Invoke a tool on a connected MCP driver... proxies the call to the external MCP server (e.g. playwright-mcp or mobile-mcp)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

call_driver_tool Rate-limited

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

FAQ

Questions about call_driver_tool

What does the call_driver_tool tool do? +

Invoke a tool on a connected MCP driver. This proxies the call to the external MCP server (e.g. playwright-mcp or mobile-mcp) and returns the result. Use list_driver_tools to see available tools and their parameters first. 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 call_driver_tool? +

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

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

Can I rate-limit call_driver_tool? +

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

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

call_driver_tool 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

call_rpc on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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