AxonFlow Governance Policies for OpenClaw
Use when setting up or hardening an OpenClaw deployment with AxonFlow governance. This skill covers self-hosting AxonFlow, plugin installation, policy configuration, and risk mitigation.
Self-Host AxonFlow
AxonFlow runs locally via Docker Compose. No LLM provider keys required — OpenClaw handles all LLM calls, AxonFlow only enforces policies and records audit trails.
Prerequisites: Docker Engine or Desktop, Docker Compose v2, 4 GB RAM, 10 GB disk.
Quick start: Clone the AxonFlow community repo, copy .env.example to .env, and run docker compose up -d. The Agent starts on port 8080 — all SDK and plugin traffic goes through this port.
Full setup instructions: Self-Hosted Deployment Guide
Install the Plugin
Install via OpenClaw's plugin manager and configure in your OpenClaw config with your AxonFlow endpoint, credentials, and high-risk tool list. Set onError: block for production (fail-closed) or allow for development (fail-open).
In community mode, clientId and clientSecret default to "community" — no credentials needed for the local developer flow. In enterprise mode, provide OAuth2 Client Credentials (Basic auth). The tenantId config field has been removed — tenant is derived server-side from credentials.
Full configuration reference: OpenClaw Integration Guide
What's Protected Automatically
AxonFlow's 80+ built-in system policies apply with no additional setup:
- Dangerous command blocking: Reverse shells,
rm -rf /, curl|bash, cloud metadata SSRF, credential file access, path traversal (10 policies)
- SQL injection: 30+ detection patterns including UNION injection, stacked queries, auth bypass
- PII detection and redaction: SSN, credit card, email, phone, Aadhaar, PAN, NRIC/FIN (Singapore)
- Code security: API keys, connection strings, hardcoded secrets, unsafe code patterns
- Prompt injection: Ignore-instruction patterns, jailbreak attempts, role hijacking
OpenClaw-Specific Hardening
For additional protection against OpenClaw-specific attack vectors, the plugin repository includes ready-to-use policy templates covering:
- Command execution blocking: Reverse shells, destructive filesystem operations, credential file access
- SSRF prevention: Cloud metadata endpoints, internal network addresses
- Agent config protection: Block writes to SOUL.md, MEMORY.md, and other identity files
- Path traversal detection: Workspace escape patterns
Full policy templates with SQL examples: Starter Policies
Top 10 Risks
| Rank |
Risk |
Hook |
| 1 |
Arbitrary command execution |
before_tool_call |
| 2 |
Data exfiltration via HTTP |
before_tool_call |
| 3 |
PII leakage in messages |
message_sending |
| 4 |
Indirect prompt injection |
before_tool_call |
| 5 |
Outbound secret exfiltration |
message_sending |
| 6 |
Malicious skill supply chain |
after_tool_call (audit) |
| 7 |
Memory/context poisoning |
before_tool_call |
| 8 |
Credential exposure |
message_sending |
| 9 |
Cross-tenant leakage |
Tenant-scoped policies |
| 10 |
Workspace boundary bypass |
before_tool_call |
Guardrails
- All policies are evaluated server-side by AxonFlow, not locally.
- High-risk tools require human approval only after AxonFlow allows the tool call. If AxonFlow blocks the tool, it stays blocked.
- The plugin verifies AxonFlow connectivity on startup.
Learn More
Get Started
Policies & Security
Governance & Compliance
Platform & Examples
Source Code
Licensing
- AxonFlow platform (getaxonflow/axonflow): BSL 1.1 (Business Source License). Source-available, not open source.
- @axonflow/openclaw plugin (getaxonflow/axonflow-openclaw-plugin): MIT. Free to use, modify, and redistribute.
- This skill: MIT-0 per ClawHub terms.
1---2name: governance-policies-23description: Set up governance policies for OpenClaw — block dangerous commands, detect PII, prevent data exfiltration, protect agent config files. Use when hardening an OpenClaw deployment with AxonFlow.4---56# AxonFlow Governance Policies for OpenClaw78Use when setting up or hardening an OpenClaw deployment with AxonFlow governance. This skill covers self-hosting AxonFlow, plugin installation, policy configuration, and risk mitigation.910## Self-Host AxonFlow1112AxonFlow runs locally via Docker Compose. No LLM provider keys required — OpenClaw handles all LLM calls, AxonFlow only enforces policies and records audit trails.1314**Prerequisites:** Docker Engine or Desktop, Docker Compose v2, 4 GB RAM, 10 GB disk.1516**Quick start:** Clone the [AxonFlow community repo](https://github.com/getaxonflow/axonflow), copy `.env.example` to `.env`, and run `docker compose up -d`. The Agent starts on port 8080 — all SDK and plugin traffic goes through this port.1718Full setup instructions: [Self-Hosted Deployment Guide](https://docs.getaxonflow.com/docs/deployment/self-hosted/)1920## Install the Plugin2122Install via OpenClaw's plugin manager and configure in your OpenClaw config with your AxonFlow endpoint, credentials, and high-risk tool list. Set `onError: block` for production (fail-closed) or `allow` for development (fail-open).2324In community mode, `clientId` and `clientSecret` default to `"community"` — no credentials needed for the local developer flow. In enterprise mode, provide OAuth2 Client Credentials (Basic auth). The `tenantId` config field has been removed — tenant is derived server-side from credentials.2526Full configuration reference: [OpenClaw Integration Guide](https://docs.getaxonflow.com/docs/integration/openclaw/)2728## What's Protected Automatically2930AxonFlow's 80+ built-in system policies apply with no additional setup:3132- **Dangerous command blocking:** Reverse shells, `rm -rf /`, `curl|bash`, cloud metadata SSRF, credential file access, path traversal (10 policies)33- **SQL injection:** 30+ detection patterns including UNION injection, stacked queries, auth bypass34- **PII detection and redaction:** SSN, credit card, email, phone, Aadhaar, PAN, NRIC/FIN (Singapore)35- **Code security:** API keys, connection strings, hardcoded secrets, unsafe code patterns36- **Prompt injection:** Ignore-instruction patterns, jailbreak attempts, role hijacking3738## OpenClaw-Specific Hardening3940For additional protection against OpenClaw-specific attack vectors, the plugin repository includes ready-to-use policy templates covering:4142- **Command execution blocking:** Reverse shells, destructive filesystem operations, credential file access43- **SSRF prevention:** Cloud metadata endpoints, internal network addresses44- **Agent config protection:** Block writes to SOUL.md, MEMORY.md, and other identity files45- **Path traversal detection:** Workspace escape patterns4647Full policy templates with SQL examples: [Starter Policies](https://github.com/getaxonflow/axonflow-openclaw-plugin/tree/main/policies)4849## Top 10 Risks5051| Rank | Risk | Hook |52|------|------|------|53| 1 | Arbitrary command execution | before_tool_call |54| 2 | Data exfiltration via HTTP | before_tool_call |55| 3 | PII leakage in messages | message_sending |56| 4 | Indirect prompt injection | before_tool_call |57| 5 | Outbound secret exfiltration | message_sending |58| 6 | Malicious skill supply chain | after_tool_call (audit) |59| 7 | Memory/context poisoning | before_tool_call |60| 8 | Credential exposure | message_sending |61| 9 | Cross-tenant leakage | Tenant-scoped policies |62| 10 | Workspace boundary bypass | before_tool_call |6364## Guardrails6566- All policies are evaluated server-side by AxonFlow, not locally.67- High-risk tools require human approval only after AxonFlow allows the tool call. If AxonFlow blocks the tool, it stays blocked.68- The plugin verifies AxonFlow connectivity on startup.6970## Learn More7172**Get Started**73- [Getting Started](https://docs.getaxonflow.com/docs/getting-started/) — quickstart for new users74- [OpenClaw Integration Guide](https://docs.getaxonflow.com/docs/integration/openclaw/) — full plugin setup walkthrough75- [Self-Hosted Deployment](https://docs.getaxonflow.com/docs/deployment/self-hosted/) — Docker Compose, prerequisites, production options7677**Policies & Security**78- [Security Best Practices](https://docs.getaxonflow.com/docs/security/best-practices/) — hardening guide for production deployments79- [Policy Enforcement](https://docs.getaxonflow.com/docs/mcp/policy-enforcement/) — how policies are evaluated at runtime80- [Policy Syntax](https://docs.getaxonflow.com/docs/policies/syntax/) — writing custom regex and rule-based policies81- [System Policies](https://docs.getaxonflow.com/docs/policies/system-policies/) — 80+ built-in policies (PII, SQLi, secrets, dangerous commands, prompt injection)82- [PII Detection](https://docs.getaxonflow.com/docs/security/pii-detection/) — SSN, credit card, Aadhaar, PAN, email, phone detection and redaction83- [Response Redaction](https://docs.getaxonflow.com/docs/mcp/response-redaction/) — how outbound content is scanned and redacted8485**Governance & Compliance**86- [Audit Logging](https://docs.getaxonflow.com/docs/governance/audit-logging/) — compliance-grade audit trails for every tool call and LLM interaction87- [Human-in-the-Loop](https://docs.getaxonflow.com/docs/governance/human-in-the-loop/) — approval gates for high-risk operations88- [HITL Approval Gates](https://docs.getaxonflow.com/docs/features/hitl-approval-gates/) — configuring approval workflows89- [Cost Management](https://docs.getaxonflow.com/docs/governance/cost-management/) — token budgets, rate limits, cost controls90- [Compliance Frameworks](https://docs.getaxonflow.com/docs/compliance/overview/) — EU AI Act, MAS FEAT, RBI, SEBI templates9192**Platform & Examples**93- [Feature Overview](https://docs.getaxonflow.com/docs/features/overview/) — full platform capabilities94- [Community vs Enterprise](https://docs.getaxonflow.com/docs/features/community-vs-enterprise/) — what's available in each tier95- [Workflow Examples](https://docs.getaxonflow.com/docs/tutorials/workflow-examples/) — multi-step governance workflows and advanced patterns96- [Banking Example](https://docs.getaxonflow.com/docs/examples/banking/) — financial services governance patterns97- [Healthcare Example](https://docs.getaxonflow.com/docs/examples/healthcare/) — HIPAA-aware agent governance98- [E-commerce Example](https://docs.getaxonflow.com/docs/examples/ecommerce/) — customer-facing agent policies99100**Source Code**101- [Plugin Source](https://github.com/getaxonflow/axonflow-openclaw-plugin) — MIT licensed102- [AxonFlow Community](https://github.com/getaxonflow/axonflow) — source-available under BSL 1.1103104## Licensing105106- **AxonFlow platform** (getaxonflow/axonflow): BSL 1.1 (Business Source License). Source-available, not open source.107- **@axonflow/openclaw plugin** (getaxonflow/axonflow-openclaw-plugin): MIT. Free to use, modify, and redistribute.108- **This skill**: MIT-0 per ClawHub terms.