openclaw - 💡(How to fix) Fix Add read-only cron inspection scope for isolated scheduled jobs [1 pull requests]

Request

Add a read-only cron inspection scope for isolated scheduled-job agent turns.

Needed read-only actions

Isolated cron jobs should be able to inspect scheduler/job health with:

• cron status
• cron list
• cron runs / recent run inspection

Actions that must remain blocked

These should stay unavailable from isolated scheduled-job context:

• cron add
• cron update
• cron run / force-run
• cron remove, except self-removal of the current job

Current behavior

An isolated scheduled job can include cron in payload.toolsAllow, but the cron tool is hardcoded to owner-only behavior in scheduled-job context. Effective behavior is self-removal only.

Observed restriction/error:

Cron tool is restricted to removing the current cron job.

This blocks cron status, cron list, and cron runs from inside the isolated job.

Use case

A read-only cron health monitor needs to verify scheduler health from inside scheduled-job isolation:

• scheduler status
• job inventory
• recent run results
• failure/delivery/skipped states
• stuck/running jobs

Without read-only cron inspection, the monitor is partially blind unless it is granted broader unsafe access such as exec, or unless a human inspects from a main session.

Why this matters

This is an observability gap, not a request for mutation capability. A health monitor should be able to report cron state without being able to create, update, remove, or force-run jobs.

Suggested shape

Expose a narrow read-only cron action scope for isolated scheduled jobs, for example:

• allow: status, list, runs
• deny: add, update, run
• deny: remove, except current-job self-removal

This would let scheduled health monitors remain read/report-only while preserving existing safety boundaries.