Getting Started
What is Node9?Quick StartHow It WorksForecastAgent IntegrationsAccount & Machine
Configuration
ConfigurationPrivacy & Cloud ModeSmart RulesEffective ConfigurationPersistent DecisionsPause & Resume
Protections
Checks ReferenceShieldsSandboxSecurity PostureContent Scanner (DLP)Trusted HostsCanary CredentialsSkill PinningRepository ScanningEgress ControlBadges
Integrations
MCP GatewayMCP ServerPython SDKGoverned Agents
Operations
Mission ControlReportSecurityAgentic Threat CoverageBlast RadiusSessions & Live ActivityRedacting Session HistoryCloud Policy Rules
Help
Help & SupportAbout Node9

About Node9 · node9 documentation

About Node9

Open-source execution security for AI agents.

What Node9 is NOT
  • Not a semantic content filter, it evaluates concrete tool calls, not AI reasoning.
  • Not a general network firewall, it gates the destinations an agent's own commands reach (node9 egress) and seals outbound at the kernel inside the sandbox; it operates on MCP tool calls at the process level.
  • Not a replacement for OS-level permissions, it is a policy layer on top of them.
What Node9 IS
  • A transparent proxy for MCP stdio tool calls.
  • A policy enforcement layer you control via JSON config.
  • An audit trail for all agent actions on your machine.
  • A dashboard (Mission Control) for real-time visibility.
Open Source
The Node9 proxy (node9-proxy) is open source. You can inspect exactly what it does to your tool calls, run it locally without any cloud dependency, and contribute improvements.

Cloud features (Mission Control, Policy Studio, team audit sync) require a Node9 workspace account and are opt-in via node9 login.