Skip to content
OpenClaw Action Firewall

OpenClaw security at the runtime hooks.

Apply action policy to OpenClaw’s native prompt, pre-tool and transcript-persistence hooks with the runtime plugin.

OpenClaw Action Firewall Native hooks
Architecture illustration. Coverage follows the configured integration and execution boundary.

Where the action needs a decision

An OpenClaw workspace can combine instructions, persistent context and tools with real side effects. A manipulated instruction can redirect an otherwise legitimate session toward an unauthorised action.

01

Install the runtime plugin

Register and enable the agenticdome-openclaw-security npm plugin, then configure the tenant’s assigned runtime connection.

02

Check the final tool call

Evaluate action context at the native pre-tool boundary, while the runtime can still prevent the tool from executing.

03

Verify the running hooks

Use the onboarding and verification workflow to establish that the intended plugin and hooks are loaded in the actual runtime.

Build a testable deployment.

Keep the plugin connection server-side and use the existing tenant onboarding flow for credentials and runtime configuration. Test prompt handling, tool rejection and transcript persistence separately.

Start with the workflow that matters.

Explore a local action-security example, plan your approach with Abi or bring your environment to a deployment review.