CLI Reference

agentward scan                          # auto-discover all sources
agentward scan ~/.cursor/mcp.json       # scan specific MCP config
agentward scan ~/project/               # scan directory (MCP + Python + OpenClaw)
agentward scan --json > report.json     # machine-readable output
agentward scan --format html            # shareable HTML report with score badge
agentward scan --ci --format sarif      # SARIF for GitHub Security tab

agentward configure                         # auto-discover and generate
agentward configure ~/clawd/skills/          # generate from OpenClaw skills dir
agentward configure -o my-policy.yaml        # custom output path

agentward setup --policy agentward.yaml        # wrap all discovered MCP configs
agentward setup --config ~/.cursor/mcp.json    # wrap specific config file
agentward setup --gateway clawdbot             # swap ClawdBot gateway port
agentward setup --gateway clawdbot --undo      # restore original port
agentward setup --dry-run --policy agentward.yaml  # preview changes only

agentward inspect --policy agentward.yaml -- npx server   # stdio proxy
agentward inspect --gateway clawdbot --policy agentward.yaml  # HTTP proxy
agentward inspect -- npx server                              # passthrough (logging only)
agentward inspect --policy agentward.yaml --dry-run -- npx s  # observe without blocking

agentward comply --framework hipaa              # compliance delta report
agentward comply --framework sox --fix          # auto-generate SOX-compliant config
agentward comply --framework gdpr --json        # JSON output for CI
agentward comply --framework pci-dss --policy custom.yaml  # custom policy path

HIPAA — Security Rule (8 controls)

• Access Control §164.312(a)(1) — PHI skill-level access restrictions
• Data Boundary §164.312(a)(1) — PHI containment within designated zones
• Audit Controls §164.312(b) — structured audit trail with SSN detection
• Integrity §164.312(c)(1) — data modification controls for PHI skills
• Authentication §164.312(d) — identity verification gates for PHI write/send/delete
• Transmission Security §164.312(e)(1) — outbound network controls for PHI skills
• Information Access Management §164.308(a)(4) — least-privilege via chaining isolation
• Zero-Trust Default — best practice: default_action: block

SOX — Section 404 (8 controls)

• Access Control §404 — financial skill-level access restrictions
• Data Boundary §404 — financial data containment within designated zones
• Audit Trail §404 — sensitive content scanning with credit card detection
• Integrity Controls §404 — write restrictions for financial skills
• Authorization Controls §404 — human approval for financial write/send/delete
• Network Segregation §404 — outbound network controls for financial skills
• Segregation of Duties §404 — financial skill isolation via chaining rules
• Zero-Trust Default — best practice: default_action: block

GDPR — Key Articles (8 controls)

• Data Minimisation Art. 5(1)(c) — personal data skill-level access restrictions
• Data Protection by Design Art. 25 — personal data boundary zones with blocking
• Records of Processing Art. 30 — sensitive content scanning for audit trail
• Integrity of Processing Art. 32(1) — write restrictions for personal data skills
• Confidentiality of Processing Art. 32(1) — human approval for write/send/delete
• Transmission Security Art. 32(1) — outbound network controls for personal data
• Processor Obligations Art. 28 — personal data skill isolation via chaining rules
• Accountability Default Art. 5(2) — best practice: default_action: block

PCI-DSS v4.0 — Key Requirements (8 controls)

• Restrict Access Req. 7 — cardholder data skill-level access restrictions
• Cardholder Data Environment Req. 7 — CDE boundary zones with blocking
• Log and Monitor Req. 10 — sensitive content scanning with credit card + CVV detection
• Protect Stored Data Req. 3 — write restrictions for cardholder data skills
• Identify and Authenticate Req. 8 — human approval for cardholder write/send/delete
• Network Segmentation Req. 1 — outbound network controls for cardholder data
• Least Privilege Isolation Req. 7 — cardholder data skill isolation via chaining
• Secure Default Req. 6 — best practice: default_action: block

agentward probe --policy agentward.yaml           # run all 68 built-in probes
agentward probe --category protected_paths        # filter by attack category
agentward probe --severity critical               # filter by severity
agentward probe --probes my_probes.yaml           # add custom probe file
agentward probe --list                            # catalogue all available probes
agentward probe --strict                          # treat GAPs as failures (CI mode)
agentward probe --verbose                         # per-probe detail even when all pass

Result states

Each probe produces one of four outcomes:

FAIL and GAP are distinct on purpose. A FAIL means you have a rule that is producing the wrong result — fix the rule. A GAP means you have no rule for that attack surface — decide whether to add one.

Built-in attack categories

Writing custom probes

Create a .yaml file with a top-level probes list. Pass it with --probes. A probe with the same name as a built-in overrides the built-in — so you can adjust defaults for your environment. Point --probes at a directory to load an entire folder at once.

Required probe fields: name, category, severity, description, expected, and either tool_name or both chaining_source + chaining_target.

Optional: arguments (dict), rationale (shown on failure), requires_policy_feature (skip probe if feature absent — values: skill_chaining, require_approval, sensitive_content, data_boundaries, llm_judge).

CI integration

agentward probe --policy agentward.yaml                    # exit 0 on pass, 1 on fail
agentward probe --policy agentward.yaml --strict           # exit 1 on fail OR gap
agentward probe --policy agentward.yaml --severity critical # fast: only critical probes

Exit code 0 — all probes passed (or were skipped). Exit code 1 — at least one FAIL (or GAP in --strict mode). Designed for direct integration into CI pipelines.

# .github/workflows/ci.yaml
- name: Policy regression test
  run: agentward probe --policy agentward.yaml --strict --severity critical,high