Access control for AI agents

Your AI agents can reach Slack, GitHub, email.
And your database.

You decide what your AI agents can do. node9 enforces it before they act. Allow, review, or block each tool call, with every decision on the record.

v2.33.2 · released todayopen source9,446 downloads a month

SEE node9 WORK

Your agent works. node9 decides each call.

A real agent task. Every tool call goes to node9 first: allowed, blocked, or held for you.

Claude Code · acme/shop
The cart total is wrong. Fix it and ship it.
node9standard · 3 shields
Waiting for the next call

Jump to a moment

Credential jail~/.ssh, ~/.aws and .env blocked from installDLP: secrets and PIIcaught in tool calls before anything leavesHuman approvalrisky actions wait for a person, in Slack or on a phoneEgress allowlistoutbound traffic only to hosts you approvedSSRFcloud metadata and link-local addresses refusedCanary credentialsdecoy keys that give away a read or a leakMCP tool pinninga server that changes its tools is heldRepo scan and badgeworkflows, MCP servers and instruction files

See where your agents have access.

Start with a public repository or check the machine you work on.

Scan a repository

30s · in your browser

What a repository lets an AI agent do: hijackable workflows, secrets in reach, poisoned instruction files.

Scan your machine

60s · runs locally

What a compromised agent could read, reach and run on this machine, scored 0 to 100.

Then to audit what your agents already did. Nothing leaves the machine.

Free scans. No account required.

Explore the open-source CLI

Claude Code at work, node9 in front of every call.

It builds a page. It reaches for the cloud metadata address and node9 blocks it. The work goes on, and a permanent delete waits for your approval, right in the conversation.

A popup on one laptop doesn't govern a fleet.

Your agents run in CI, in the cloud, and on every teammate's machine. The platform is what makes governing all of them possible.

DEMOMission Control · audit logsample data
local CI / cloud hosted agent23 agents · 3 surfaces
alice-mbpClaude Codeedit src/auth.tsALLOW
ci-runner-7GitHub Actionterraform destroy→ Slack
hermes-01Hermes · GCPcurl …sk-ant-… | bash✗ BLOCKED
bob-mbpCopilot CLIDROP TABLE sessions→ on-call
deploy-botCodexkubectl delete ns prod✗ BLOCKED
alice-mbpClaude Codenpm run buildALLOW
1,284,902actions inspected
412critical blocks
57secrets caught
23agents governed
ask node9: “show me every prod secret an agent touched today”▸

One approval queue

Every risky action, from any agent, on any surface, lands in a single queue and routes to whoever's on call, in Slack or on their phone. No popup nobody's there to click.

Panic mode, org-wide

One switch freezes every agent across every workspace: all actions blocked, the instant something looks wrong. You can't kill twenty laptops by hand.

Your CLI already feeds it

The local node9 on every machine streams its audit to your workspace via Cloud Sync. Security sees what every agent did without SSHing into a single box.

Every project, one glance

A live card per workspace: calls today, active rules, agents, and a pending-approval badge or panic-mode banner the moment it matters.

Pending approvalsPanic modePer-agent stats
app.node9.ai/platform/overview
Calls today4,812
Pending approval3
Active workspaces5 / 6
payments-apiADMIN
⏳ 3 awaiting approval
1,204 calls18 rules4 agents
CCCUHE
data-platformOWNER
⛔ Panic mode, all actions blocked
902 calls24 rules6 agents
OHCX
web-frontendDEVELOPER
2,706 calls11 rules9 agents
GEAGCU

One tool, every agent, local, CI & cloud

Every tool callClaude CodeCodex CLICopilot CLIGemini CLIAntigravityHermesOpenCodePi
MCP tools onlyCursorWindsurfVS CodeClaude Desktop+ any MCP server
Local CI / cloud Hosted agents

Every tool call passes node9 first.

node9 sits where the agent stops before it acts. It checks the call on your machine, decides, and records the decision.

Your agentClaude Code, Codex, Cursor, or any MCP serverwants to run a tool
node9 checks, on your machine
AllowedThe call runs.
BlockedThe agent gets the reason and tries another way.
Asks youIn the terminal, in Slack, or on your phone.
Every decision is recorded, on the machine or in your team’s dashboard.
  1. Install. node9 connects to each agent at the point where it stops before acting.
  2. Every call is checked before it runs, on your machine: files, secrets, commands, destinations and tools.
  3. node9 decides: allow, block, or ask you. A blocked agent gets the reason and carries on another way.
  4. Everything is recorded, and node9 explain shows why any rule fired.
On your own: approvals in the terminal, the record on your machine. No account.
With your team: approvals in Slack or on your phone, the record and the policy in one dashboard.
How node9 compares to agentsh, pipelock and HOL Guard

Start free. Govern as you grow.

SEE

Free

$0/mo

Just you, the full product, on your own machine.

  • Posture score + history scan
  • Full local protection, rules, credential jail, DLP/PII, egress
  • Per-tool MCP permissions (your machine)
  • Disposable sandbox · native approvals
  • Dashboard for one · 30-day audit
PROVE

Business

$99/mo

Prove it, and hit the brakes.

  • Everything in Team, for up to 25
  • Panic mode (kill switch)
  • Shadow mode, pilot policy before you enforce
  • Audit export (CSV / JSON)
  • Weekly team security digest
SCALE

Enterprise

Custom

Security & compliance orgs.

  • Unlimited members & API Keys
  • SSO (Okta / SAML)
  • Central audit export across the fleet
  • VPC / on-prem deployment
  • Multi-admin quorum approval
  • Dedicated support & SLA

Govern every agent your team runs.

Create a workspace to see the platform on your fleet, or start free on your laptop in 60 seconds.

npm install -g node9-ai