In-browser ~60Hz behavior tree execution engine with reactive triggers and safety guardrails.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
load_behaviorInject, initialize, or hot-swap a behavior tree instance in the browser runtime.Inject, initialize, or hot-swap a behavior tree instance in the browser runtime.
No input schema was published for this tool.
set_parametersDynamically update or query execution parameters for the active behavior runtime.Dynamically update or query execution parameters for the active behavior runtime.
No input schema was published for this tool.
get_statusQuery active behavior execution status, current node path, tick count, duration, and error state.Query active behavior execution status, current node path, tick count, duration, and error state.
No input schema was published for this tool.
abort_behaviorImmediately halt, pause, or resume behavior execution and disengage active inputs.Immediately halt, pause, or resume behavior execution and disengage active inputs.
No input schema was published for this tool.
register_triggerConfigure and manage reactive interrupt triggers with priority preemption and cooldown guards.Configure and manage reactive interrupt triggers with priority preemption and cooldown guards.
No input schema was published for this tool.
replay_recordingCapture or replay deterministic browser action sequences with adaptive timing.Capture or replay deterministic browser action sequences with adaptive timing.
No input schema was published for this tool.
get_metricsRetrieve runtime execution telemetry, tick durations, stuck events, and category statistics.Retrieve runtime execution telemetry, tick durations, stuck events, and category statistics.
No input schema was published for this tool.
manage_behaviorsCRUD operations for immutable JSON behavior tree definitions with SHA-256 tree hash verification.CRUD operations for immutable JSON behavior tree definitions with SHA-256 tree hash verification.
No input schema was published for this tool.
manage_blackboardRead, write, or query shared behavior tree blackboard state variables.Read, write, or query shared behavior tree blackboard state variables.
No input schema was published for this tool.
manage_runtime_dbDatabase maintenance, diagnostics, SHA-256 Merkle audit verification, checkpoints save/restore, and diffs.Database maintenance, diagnostics, SHA-256 Merkle audit verification, checkpoints save/restore, and diffs.
No input schema was published for this tool.
10 of 10 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
In-browser ~60Hz behavior tree execution engine with reactive triggers and safety guardrails.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
76 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+64 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.