unload_toolset
Remove a dynamically loaded toolset from the current session to free up context. Cannot unload toolsets from the initial preset.
This record as markdown: /tools/io-github-homenshum-nodebench/unload-toolset.md
What unload_toolset does on Nodebench
AI agents call unload_toolset to permanently remove resources in Nodebench, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why unload_toolset is rated Critical
Unloading a toolset removes it from the session irreversibly (within that session context) — the tool does not merely update or toggle state, it removes/purges the toolset from availability. While not data destruction in the traditional sense, the operation is not easily reversible mid-session and constitutes removal of a resource. Severity is medium since it affects session capabilities rather than persistent data.
From the tool's definition 'Remove a dynamically loaded toolset from the current session' and 'Cannot unload toolsets from the initial preset'
Attacks that exploit this kind of access
The rule that runs unload_toolset 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 unload_toolset, this is the rule to start with:
unload_toolset is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every unload_toolset call is checked against it from then on.
Questions about unload_toolset
Remove a dynamically loaded toolset from the current session to free up context. Cannot unload toolsets from the initial preset. It is categorised as a Destructive tool in the Nodebench MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Nodebench MCP server in PolicyLayer and add a rule for unload_toolset: 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.
unload_toolset is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the unload_toolset 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 unload_toolset. 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.
unload_toolset 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