跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
安全

approve-exempt

Approve pending Harness STO security exemptions (waivers) at their current scope or elevate them to Project, Org, or Account scope. Users say "approve" for both in-scope approval and higher-scope elevation — do not require the word "promote". Supports approving one exemption or a mixed list where each row has a different approval scope. Default workflow lists pending exemptions in chat (paginated preview) so the user picks by row number — no copying from the Harness UI. Use when a user wants to approve, sign off on, or clear pending exemptions, waive approvals, org-wide approval, or account-wide approval. Trigger phrases: approve exempt, approve exemption, approve waiver, sign off exemption, clear pending exemption, approve for org, approve for account, org-wide approval, account-wide approval, pending exemptions.

Harness · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add harness/harness-skills --skill approve-exempt

技能说明


name: approve-exempt description: >- Approve pending Harness STO security exemptions (waivers) at their current scope or elevate them to Project, Org, or Account scope. Users say "approve" for both in-scope approval and higher-scope elevation — do not require the word "promote". Supports approving one exemption or a mixed list where each row has a different approval scope. Default workflow lists pending exemptions in chat (paginated preview) so the user picks by row number — no copying from the Harness UI. Use when a user wants to approve, sign off on, or clear pending exemptions, waive approvals, org-wide approval, or account-wide approval. Trigger phrases: approve exempt, approve exemption, approve waiver, sign off exemption, clear pending exemption, approve for org, approve for account, org-wide approval, account-wide approval, pending exemptions. metadata: author: Harness version: 1.0.0 mcp-server: harness-mcp-v2 license: Apache-2.0 compatibility: Requires Harness MCP v2 server (harness-mcp-v2)

Approve Exemption

Approve one or more Pending STO security exemptions. This skill covers the approval workflow after someone has requested an exemption (see /exempt-vuln for creation).

Pending scope is only PROJECT, PIPELINE, or TARGET. Exemptions are requested at project, pipeline, or target scope only (All Issues → project; Vulnerabilities tab → project, pipeline, or target). STO does not create pending requests at org or account scope — those wider scopes exist only after elevation on approve (body.scope ORG or ACCOUNT). You will not see scope: ORG or scope: ACCOUNT on rows from status: Pending in normal flows. If a list row shows ORG/ACCOUNT, it is already approved/widened (re-approve or a different workflow), not a fresh pending request this skill targets.

Harness exposes two different "scope" ideas — do not mix them up:

ConceptWhat it controlsHow you use it
Listing scopeWhich project's exemption queue you readAlways list at project scope. Never pass resource_scope='account' or 'org' to harness_list.
Approval scopeWhere the exemption becomes effective after approvalPassed as body.scope on harness_execute — CURRENT, PROJECT, ORG, or ACCOUNT.

Users almost always say approve, even when they want org- or account-wide coverage. Treat "approve for org", "org-wide", and "at account level" as approve with elevation — the MCP server routes those to the promote endpoint internally. You never need a separate action='promote' call; always use action='approve' with the right body.scope.

Keep the Harness UI out of the loop. Do not ask the user to copy issue titles, CVEs, or exemption IDs from the platform. Your default opening move is to list pending exemptions in chat, show a numbered table, report total, and let them pick by row number (or narrow with search if they volunteer a keyword). Pagination surfaces more rows on request — you never dump the full queue at once.

Instructions

Step 1 — Establish project context

You need org and project unless they are already in session defaults or a pasted Harness URL provides them.

Exemptions list URL shape (auto-extracts org/project):

…/ng/account/{accountId}/all/orgs/{org}/projects/{project}/sto/exemptions

Step 2 — Surface pending exemptions (default opening move)

Unless the user already picked row numbers from a table you showed in this same session, call harness_list before asking them to choose anything. Do not send them to the Harness UI.

Show a paginated preview, not the whole queue

Chat is a narrow surface — dumping 50 pending rows is unreadable. Default behavior:

  1. Call harness_list with status: Pending, size: 5, page: 0 (unless org/project are still unknown — resolve those first).
  2. Read total from the response.
  3. Render the table from items[] following _display_hint. Number rows 1–N to match _action_id_by_row (1-based).
  4. Tell the user how many pending exemptions exist and how to proceed:
    • If total ≤ 5: show every row; ask which to approve.
    • If total > 5: show the first page and say something like:

      {total} pending exemption(s) in this project. Showing rows 1–5 below. Pick by number (e.g. 1, 1 and 3, 2-4), say next for the next page, or give a search term to narrow (CVE, requester, issue title).

  5. For next page, follow _nextPageHint exactly — keep size, status, and any search identical; only increment page.
harness_list
  resource_type: "security_exemption"
  org_id: <org>
  project_id: <project>
  filters:
    status: "Pending"
    size: 5
    page: 0
    search: "<optional — only when user narrows>"

Rules:

  • status must be a single value (Pending), not comma-separated.
  • Default size: 5 inside filters on every call in a pagination session. Do not bump size mid-session unless the user explicitly asks for a larger page (e.g. "show 10").
  • Keep size and all other filters identical when paginating; follow _nextPageHint verbatim.
  • Never pass resource_scope, and never set org_id / project_id to words like org or account — those are approval-scope phrases, not list overrides.

The list response is optimized for chat:

  • items[] — display fields only (issue_title, severity, type, requested_by, target, scope, reason, …). No exemption IDs in the table.
  • _action_id_by_row — maps row number (1-based on the current page) → exemption_id for execute calls.
  • _display_hint — column layout; follow it.
  • Each row's scope is the exemption's requested scope — expect only TARGET, PIPELINE, or PROJECT for pending rows.

The selection prompt

After showing the table, always include:

  1. total pending count (project-wide, not just this page)
阅读完整来源 ↗