Install the runtime plugin
Register and enable the agenticdome-openclaw-security npm plugin, then configure the tenant’s assigned runtime connection.
Apply action policy to OpenClaw’s native prompt, pre-tool and transcript-persistence hooks with the runtime plugin.
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.
Register and enable the agenticdome-openclaw-security npm plugin, then configure the tenant’s assigned runtime connection.
Evaluate action context at the native pre-tool boundary, while the runtime can still prevent the tool from executing.
Use the onboarding and verification workflow to establish that the intended plugin and hooks are loaded in the actual runtime.
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.
Explore a local action-security example, plan your approach with Abi or bring your environment to a deployment review.