Critical-risk tools in Nodebench
10 of the 824 tools in Nodebench are classified as critical risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at critical risk
-
abandon_cycleDestructiveAbandon an active verification cycle that will not be completed. Use this to clean up orphaned or stale cycles.
-
archiveDocumentDestructiveArchive (soft-delete) a document and all its children recursively.
-
cleanup_stale_runsDestructiveClean up orphaned eval runs stuck in
-
deeptrace_revoke_passportDestructiveRevoke an agent
-
delete_learningDestructiveDelete a learning by key. Use when a learning is outdated or incorrect.
-
delete_sandbox_policyDestructiveDelete a sandbox policy. Fails if any active sessions are using it.
-
deleteAgentMemoryDestructiveDelete stored memory by key
-
removeDocumentFromFolderDestructiveRemove a document from a folder.
-
share_revoke_packet_linkDestructiveRevoke a local share link so it no longer counts as active.
-
unload_toolsetDestructiveRemove a dynamically loaded toolset from the current session to free up context. Cannot unload toolsets from the initial preset.
Attacks that target this class
Critical-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.