Cairn

Cron jobs bypassing disabled toolset restrictions

NousResearch/hermes-agent · cluster 25752 · cron

Data as of

Nothing open on GitHub. Fix merged in #31947. Check it covers your case.

The short answer

0open issues
0open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #31947. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #31947. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and PRs concern a security/configuration gap where cron job per-job overrides could bypass the agent's disabled_toolsets denylist. Multiple fix attempts address enforcing toolset restrictions during cron scheduling.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #31947 fix(cron): layer agent.disabled_toolsets onto cron baseline (#25752, salvage)

    merged to main

    files: cron/scheduler.py, scripts/release.py, tests/cron/test_scheduler.py

4 PRs closed without merging

From the close comments: superseded by another PR 2 · duplicate 1 · other 1

  • #25780 fix: honor cron toolset denylist · superseded by another PR → 0c3e34e, #31947, #25752, #25786, #25842, #25815, #25780
  • #25786 fix: honor disabled toolsets in cron runs · other → #25780
  • #25842 fix(security): enforce disabled_toolsets in cron per-job overrides (#25752) · superseded by another PR → 0c3e34e, #31947, #25752, #25786, #25842, #25815, #25780
  • #25937 fix(cron): cap job toolsets by config · duplicate → #25752, #25780, #25786, #25815, #25842
Closed issues · 1
  • Closed#25752cron/scheduler.py:74-86 bypasses agent.disabled_toolsets via LLM-supplied enabled_toolsets
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.33: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
cron
Merged PRs
#31947
Closed issues
1
Attempts
4 PRs closed without merging
Fix link checked
25 May 2026

For your agent

The same facts, typed.

cluster/25752.json
cluster/25752.md