HOL Guard rule for `approve_plugin`?
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 56/100
- issue の種類
- 機能追加
- 明瞭さ
- 明確に書かれている
- 活発さ
- 活発
- 技術スタック
- github, typescript
調査の方向性
Read the upstream community-plugins behavior and the HOL Guard MCP contribution guide and matching Builder example linked in the issue. Export the complete tools/list inventory, generate and review the profile for approve_plugin, and retain existing handling for get_plugin and unknown tools. Validate and preview the kit, run the named MCP contribution and trust checks, then submit a draft PR with the profile, behavior cases, and validation results.
索引モデルが issue の本文から書いたものです。
説明
Hey, we maintain HOL Guard. For people using community-plugins through an AI agent, an optional Guard profile would ask for human approval before the approve_plugin action.
Would you contribute a profile covering approve_plugin? The first draft can focus on that operation and get_plugin as the comparison case. The Builder handoff below is specific to this project; you generate and review the files, then open your PR. A draft with the reviewed profile and validation results is enough to start review. Local Guard protection is free and needs no account. The extension stays opt-in, and your repo needs no code or CI changes.
Builder handoff for this project
Scope: cursor/community-plugins, approve_plugin, and the get_plugin comparison. Upstream reference.
Existing safeguard documented by the project:
Write tools are rate-limited per admin (
mcp-moderationVercel Firewall rule), and every change from the web admin or MCP is recorded in the append-onlyplugin_moderation_eventstable.
You can give these instructions to your coding agent:
- Work in your own fork/branch of
hashgraph-online/hol-guard. Export the complete MCP tools/list inventory using your project's documented workflow, including every page. Confirm the package/launcher or HTTPS identity and version from your own documentation; do not guess them from the repository name. - Follow the matching Builder example to generate a review kit from that saved export. Use physical paths without symlink components and a new output directory whose parent already exists. The Builder reads the export offline; it does not run your tool.
- Propose review for
approve_plugin. Useget_pluginas the safe comparison case, retaining its existing handling. Unknown tools inherit existing policy. Do not add an allow default based only on tool annotations or a remote server name. Review the generated decisions against the upstream behavior; record the rationale and public source references in a copy of review.json and set reviewed=true for the decisions you reviewed. Preserve the discoveryDigest, operation IDs, other entries, and supported riskClasses. Regenerate withextensions generate --from snapshot, using the original discovery.json and your explicit review file. - Run
hol-guard extensions validateon that reviewed kit. Previewhol-guard extensions applyagainst your fork, inspect the file plan, and apply only with its printed--expected-plandigest. Keep the MCP JSON contract under contributions/mcp-servers/ and the external trust binding. Run the MCP contribution test and trust checks named in the MCP guide. Record the risky and comparison-tool decisions in your PR. The MCP Builder does not emit a command fixture; do not invent a command-source document or a Python detector. Follow the contribution checks for this contribution type. - Review the full diff and behavior cases, then open your own draft PR with the contribution files and validation results. Explain what needs approval and what retains its existing handling. Keep the contribution External and off until locally enabled. Do not add secrets, change your source repository's CI, or enable Guard protections as part of generating the contribution.
A draft containing the profile/source and meaningful behavior cases is enough to begin review. Report a failed Builder command with its error before working around it.
- 主要言語
- TypeScript
- スター
- 4k
- フォーク
- 674
- 平均マージ
- 8分
- マージ済み PR(30日)
- 28
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
cursor/community-plugins のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 73/100
cursor/community-plugins#572 ·
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 74/100
cursor/community-plugins#567 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 73/100
cursor/community-plugins#543 ·
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 66/100
cursor/community-plugins#518 ·
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 70/100
cursor/community-plugins#516 ·
メンテナーはふだん 1 日以内に返信
cursor/community-plugins の issue をすべて見る
似ている issue
-
P2
難易度 1/5 1時間未満 初心者へのやさしさ 84/100
メンテナーはふだん 1 日以内に返信
-
bug ready-for-human
難易度 2/5 1〜3時間 初心者へのやさしさ 60/100
LucasSantana-Dev/Lucky#3150 ·
メンテナーはふだん 1 日以内に返信
-
enhancement good first issue priority: low size: XS
難易度 2/5 1〜3時間 初心者へのやさしさ 88/100
メンテナーはふだん 1 日以内に返信
-
area: testing bug priority: low
難易度 2/5 1〜3時間 初心者へのやさしさ 87/100
snapotter-hq/SnapOtter#5099 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
EveryInc/compound-engineering-plugin#2091 ·
メンテナーはふだん 1 日以内に返信