ACT, or Agent Component Tools, is a hardened AI toolchain for building sandboxed components for AI agents. It is aimed at environments where a simple local run is not enough, and it addresses the problem of third-party tools arriving with broad access, opaque provenance, and no declared execution bounds.
Its components are built as WebAssembly-based units and described as self-documenting. The workflow shown on the site includes writing a tool in Rust, Python, Go, C++, or any language that compiles to WebAssembly, compiling it into a single .wasm component, and then pushing it to an OCI registry. The component format can include schemas, descriptions, examples, and agent skills baked into the binary, and the published artifact carries signed provenance through a GitHub Actions attestation linking the artifact to its source commit. The system also uses deterministic builds so the same SHA256 can be produced on every machine.
ACT describes its runtime model as sandboxed by wasmtime with zero ambient access, meaning no filesystem access, no outbound network, and no syscall surface unless the operator explicitly grants it. It also uses a capability ceiling: components declare what they need at build time, operators grant what they are willing to allow, and the host enforces the intersection. The site says components can run over MCP, CLI, HTTP API, or in the browser, and the example command line shows a pull-and-run flow from an OCI registry. The toolchain is presented as suitable for AI agents and for humans reading the embedded documentation without running the component first.
The page includes npm installation commands for @actcore/act and @actcore/act-build.
ACT sits in PulseGate's AI security & guardrails category. It focuses on securing and standardizing third-party AI agent tools with sandboxing and provenance. ACT is an open-source project aimed at AI developers. The project is open source (Apache-2.0). It runs on the web, the command line, and API, and it can be self-hosted.
ACT first shipped in 2026. Development happens publicly on GitHub with 23 commits in the last 90 days. Among its 5 catalogued features are sandboxed components, signed artifacts, and capability ceilings. It exposes integrations via a public API and an MCP server.
Summary written by a language model from the project’s public pages.
What PulseGate has recorded for this listing
Closest matches by what these projects do