connect_mcp_driver

Connect to an external MCP server and make its tools available through nodebench-mcp. Predefined drivers:

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/connect-mcp-driver.md

WHAT IT DOES

What connect_mcp_driver does on Nodebench

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

This tool establishes a connection to an external MCP server and imports its tools into the current environment. This is an Execute-category action because it triggers an external operation whose effects depend on arguments (which server is connected).

From the tool's definition 'Connect to an external MCP server and make its tools available through nodebench-mcp' — this triggers an external connection and dynamically exposes additional tools from a remote server

Attacks that exploit this kind of access

RECOMMENDED RULE

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

connect_mcp_driver Rate-limited

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

FAQ

Questions about connect_mcp_driver

What does the connect_mcp_driver tool do? +

Connect to an external MCP server and make its tools available through nodebench-mcp. Predefined drivers:. 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 connect_mcp_driver? +

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

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

Can I rate-limit connect_mcp_driver? +

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

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

connect_mcp_driver 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

adb_connect_device on Android Forensics ADB MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

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