nodrail
INTEGRATIONS

Use APF with your agent harness

Choose the integration that controls your tools. Claude Code can load local APF files. A custom harness can embed the evaluator. Cloud-connected plugins and SDKs add shared decisions and approval by a person for the paths they cover.

Local hook and Cloud plugin

Claude Code

Local APF. The local Claude Code hook reads your YAML before a covered tool call. For review decisions it can ask the person at the keyboard. Set up the local hook.

Cloud plugin. The plugin checks covered shell commands, file changes, MCP tools and supported web operations before they run. Reads through Read, Grep and Glob receive local checks for credential locations rather than being sent to Cloud.

Requires Node.js 22 or later and Claude Code 2.1.295 or later.

If it fails The configured onFailure behavior blocks calls when the hook crashes or cannot run. An agent or process that can alter hook settings can bypass that boundary.

Cloud plugin

Codex

Cloud plugin. The published Codex setup checks workspace policies with a Nodrail credential. Coverage includes listed shell tools, file changes through apply_patch, and MCP tools. Hosted web search runs outside this hook, and new tool names are not automatically covered.

Requires Node.js 22 or later and Codex 0.155 or later. After installing the plugin, approve its hooks in /hooks; no calls are checked before activation.

If it fails If the running hook cannot reach Nodrail or encounters a check failure, it blocks the covered action. If the hook cannot start at all, such as when Node.js is missing, Codex can run the tool. This startup failure is a runtime limitation; do not rely on this plugin alone for containment.

Cloud SDK

TypeScript SDK

Covers The tools you wrap with guard() before passing them to your agent. The client requires a fresh authorization for the exact covered call. Unwrapped functions and provider-hosted tools are outside that boundary.

Requires Supported object shapes do not mean every version of a framework has been tested; use the maintained examples and check your installed version.

If it fails A denied request, expired wait, missing credential or check error blocks invocation through the wrapper.

Cloud server tools

MCP server tools

Covers Supported tool registrations on a server you control, once you call guardMcpServer() before registering them. It is a server-side integration, not a network-wide gateway for every MCP connection.

Requires Add the guard first: registering tools before adding it is not a supported shortcut.

If it fails Other servers, unsupported registration shapes and routes outside the guarded server need their own controls.

Your own agent harness

Load the APF file into the open-source engine. Describe each covered tool call using the operation and resource your policy expects. Invoke the tool on allow, stop on denial, and wait on a call that requires approval until your integration receives a valid decision. Treat none as unresolved. An adapter can reuse a policy only for the actions and facts it can faithfully describe.

GitHub merge check (pilot)

We tested a required status on a protected branch in our public plugins repository. After a new push, GitHub held the merge until QA reviewed the new commit. We ran the adapter locally and triggered each review and status update ourselves. The check uses runs and gates, which are in preview.

Read the GitHub merge check pilot.

Before you rely on a connection

Test an allowed call, a denied call, an unknown permission and a failed connection in an isolated test environment. Check the actual tool invocation, not just the decision shown on screen. Protect the settings and credentials that determine whether the integration runs.

The plugin hook passes Windows tests, but real-agent Windows compatibility has not yet been established in the maintained plugin documentation. Check release notes for your operating system and runtime. Client APIs remain a developer preview before 1.0.

Share decisions with your team

Connect Claude Code, Codex, TypeScript tools or MCP servers to one Cloud workspace with shared rules, approvals and history.

GET STARTED

Try your first policy

Start with a local rule, then connect it to the tools your agent uses.