Skip to content

security audit --deep fails with missing scope: operator.read when probing gateway #47987

@ArchMa9e

Description

@ArchMa9e

Description

When running openclaw security audit --deep, the command attempts to connect to the gateway WebSocket but fails with:

⇄ res ✗ status 0ms errorCode=INVALID_REQUEST errorMessage=missing scope: operator.read

This causes the gateway.probe_failed warning in the security audit output:

gateway.probe_failed Gateway probe failed (deep)
  missing scope: operator.read
  Fix: Run "openclaw status --all" to debug connectivity/auth, then re-run "openclaw security audit --deep".

Steps to Reproduce

  1. Run openclaw security audit --deep
  2. Observe the warning about gateway.probe_failed
  3. Check gateway logs - see missing scope: operator.read errors

Expected Behavior

The security audit --deep command should have sufficient permissions to probe the gateway, or should handle this gracefully without errors.

Environment

  • OpenClaw version: 2026.3.13
  • Node: v22.22.1
  • OS: Ubuntu Linux 6.8.0-55-generic

Additional Context

The connection ID in logs matches the timing of running security audit --deep, confirming it's the audit command itself connecting to the gateway with insufficient token scope.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions