Skip to content
OpenClaw integration

Action security for OpenClaw.

Attach the native OpenClaw Action Firewall plugin.

Get the package and source.

Connect the execution boundary.

Install and enable the runtime plugin, then verify native prompt, pre-tool and transcript hooks. The Python CLI helps onboarding; the npm plugin performs runtime interception.

An example to test

A workspace instruction tries to redirect a tool toward data export. Evaluate the actual pre-tool call and verify the block in the installed runtime.

Illustrative workflow, not a customer deployment or a measured result.

Before connecting live policy

  1. Identify the handler that actually performs the side effect.
  2. Provide trusted identity, purpose and final action arguments.
  3. Configure the tenant’s assigned runtime and keep API credentials server-side.
  4. Test allowed, blocked and unavailable paths before production.

Integration example

Adapt this existing SDK pattern to your application. Names such as the agent, handler and session refer to your own objects. Follow the package documentation for compatible versions and complete setup.

Python 3.11+ is required for the Python SDK and local demo commands.

# PyPI installs the local Integration Copilot and verification CLI.
python -m pip install --upgrade "agenticdome-python-sdk"

# Configure the npm runtime plugin with your assigned tenant connection.
export AGENTICDOME_API_BASE="https://your-sidecar.example.com"
export AGENTICDOME_API_KEY="your_api_key"
export AGENTICDOME_TENANT_ID="your_tenant_id"
export AGENTICDOME_PLATFORM="openclaw"

# Register and enable the native OpenClaw TypeScript plugin.
openclaw plugins install npm:agenticdome-openclaw-security
openclaw plugins enable agenticdome-security
openclaw config set plugins.entries.agenticdome-security.hooks.allowConversationAccess true
openclaw gateway restart

# Fail closed unless the real runtime loaded the exact certified hooks.
agenticdome openclaw protect

Python demo commands evaluate fixed inputs against a bundled local policy; they do not instantiate the selected framework or prove a live integration. The TypeScript client and OpenClaw runtime plugin need their documented tenant configuration.

Prefer a gateway for service calls?

For compatible MCP, API, GraphQL and A2A requests, configure the assigned sidecar gateway without adding AgenticDome SDK hooks. Use the SDK path above for internal tools and richer framework context.

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.