One primitive, four kinds of system
A tool is anything an agent reaches outside itself: a host, an API, a database or an application — each behind a connector with its own permissions.
Hosts
Enrolled Linux, macOS and Windows hosts, read-only by default.
Read-only execution policy is the default on every enrolled host; the full policy is an explicit, per-host choice.
Host investigations show the commands that ran, their exit codes and output, per host.
A host joins the fleet with one install command and an enrollment token; revoking the host unpairs it.
APIs, databases and applications
The same connector model extends to the rest of your stack.
Agents reach your systems through the MCP servers you connect in the console. A token you enter there is sealed, never shown again, and acts only with the permissions your system gives it; a connector that runs on one of your hosts keeps its token in that host's own connector file.
Proof of depth
Host tools are read-only by default. The Security and Technical packs compose them into named agents — see how far that composition goes:
- Security pack
- Technical pack
Bring one question of your own.