hermes - 💡(How to fix) Fix [Feature] SSL-based Risk Policy Engine cho Skills [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#17947Fetched 2026-05-01 05:54:53
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
labeled ×4

Fix Action

Solution

  • Thêm policy engine đọc risk score từ SSL index
  • Skills với risk >= 7 cần explicit user approval
  • Skills với risk >= 10 bị block hoàn toàn
RAW_BUFFERClick to expand / collapse

Problem

Hiện tại SSL risk scores được compute nhưng không có enforce mechanism. Agent có thể chạy HIGH/CRITICAL risk skills mà không có approval.

Stats

  • CRITICAL (>= 7): 14 skills (12%)
  • HIGH (5-6): 19 skills (16%)
  • MEDIUM (3-4): 39 skills (33%)
  • LOW (0-2): 48 skills (40%)

Solution

  • Thêm policy engine đọc risk score từ SSL index
  • Skills với risk >= 7 cần explicit user approval
  • Skills với risk >= 10 bị block hoàn toàn

Skills cần approval (risk >= 7)

  • email.himalaya (credential + network + file)
  • social-media.xurl (credential + network)
  • productivity.airtable (credential + network + file)
  • research.polymarket (credential + network + file)
  • productivity.google-workspace (credential + network)
  • research.llm-wiki (credential + network + file)

Implementation Reference

  • SSL Normalizer: ~/.hermes/scripts/ssl_normalizer.py
  • Skill Discovery: ~/.hermes/scripts/skill_discovery.py
  • SSL Index: ~/.hermes/skills/.ssl_index.json

Manual Work Needed

  • User confirmation approach (Telegram inline button? CLI confirm?)
  • Policy exceptions UI

Effort: Dev

extent analysis

TL;DR

Implement a policy engine to enforce SSL risk scores, requiring explicit user approval for skills with a risk score of 7 or higher.

Guidance

  • Review the ssl_normalizer.py and skill_discovery.py scripts to understand the current SSL risk score computation and skill discovery processes.
  • Develop a policy engine that reads risk scores from the ssl_index.json file and enforces the proposed rules (e.g., blocking skills with a risk score of 10 or higher).
  • Design a user confirmation approach, such as a Telegram inline button or CLI confirmation, to obtain explicit approval for high-risk skills.
  • Consider implementing a UI for policy exceptions to handle edge cases.

Example

No code snippet is provided due to the lack of specific implementation details.

Notes

The proposed solution requires additional development effort to implement the policy engine, user confirmation approach, and policy exceptions UI.

Recommendation

Apply the proposed workaround by implementing a policy engine to enforce SSL risk scores, as it addresses the current lack of enforcement mechanism and provides a clear path forward for mitigating high-risk skills.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix [Feature] SSL-based Risk Policy Engine cho Skills [1 participants]