disconnect_driver
Disconnect from an external MCP driver and shut down its child process. Use this to clean up or to reconnect with different settings.
This record as markdown: /tools/io-github-homenshum-nodebench/disconnect-driver.md
What disconnect_driver does on Nodebench
AI agents invoke disconnect_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.
Why disconnect_driver is rated High
This tool actively kills/shuts down a child process and severs a connection. It is an operational action (process termination) that affects running infrastructure. While it could be seen as somewhat reversible (you can reconnect), shutting down a process is an Execute-level action with medium severity since misuse could disrupt active integrations or workflows.
From the tool's definition 'Disconnect from an external MCP driver and shut down its child process' — terminates a running process
Attacks that exploit this kind of access
The rule that runs disconnect_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 disconnect_driver, this is the rule to start with:
disconnect_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every disconnect_driver call is checked against it from then on.
Questions about disconnect_driver
Disconnect from an external MCP driver and shut down its child process. Use this to clean up or to reconnect with different settings. 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.
Register the Nodebench MCP server in PolicyLayer and add a rule for disconnect_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.
disconnect_driver is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the disconnect_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.
Set action: deny in the PolicyLayer policy for disconnect_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.
disconnect_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.
More on Nodebench, and thousands of servers like it.
Across the catalogue