exempt-vuln
Create Harness STO security exemptions (waivers) for vulnerabilities found by SAST, SCA, DAST, secret, container, or IaC scanners. Works from both entry points in the Harness UI: the Vulnerabilities tab of a specific pipeline execution (Target, Pipeline, or Project scope) and the All Issues page (Project scope only). Supports single creates with per-row error tolerance and bulk creates of up to 100 issues in one all-or-none transaction. The requester is derived automatically from the authenticated user. Use when a user wants to exempt a vulnerability, waive a CVE, suppress a security finding, mark a finding as a false positive, accept the risk, or exempt several vulnerabilities at once. Trigger phrases: exempt vuln, exempt vulnerability, exempt CVE, waive vulnerability, create exemption, suppress security issue, false positive, accept risk, ignore CVE, bulk exempt.
Harness · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add harness/harness-skills --skill exempt-vuln技能说明
name: exempt-vuln description: >- Create Harness STO security exemptions (waivers) for vulnerabilities found by SAST, SCA, DAST, secret, container, or IaC scanners. Works from both entry points in the Harness UI: the Vulnerabilities tab of a specific pipeline execution (Target, Pipeline, or Project scope) and the All Issues page (Project scope only). Supports single creates with per-row error tolerance and bulk creates of up to 100 issues in one all-or-none transaction. The requester is derived automatically from the authenticated user. Use when a user wants to exempt a vulnerability, waive a CVE, suppress a security finding, mark a finding as a false positive, accept the risk, or exempt several vulnerabilities at once. Trigger phrases: exempt vuln, exempt vulnerability, exempt CVE, waive vulnerability, create exemption, suppress security issue, false positive, accept risk, ignore CVE, bulk exempt. 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)
Exempt Vulnerability
Create a security exemption (waiver) for one or more Harness STO vulnerabilities. STO has two places a user can request an exemption from, and each one allows a different set of scopes:
| Where the user is in the Harness UI | Scopes they can request |
|---|---|
| Vulnerabilities tab of a specific pipeline execution | This Project, This Pipeline, This Target |
| All Issues page (the project-wide baseline) | This Project only |
The reason for the difference is simple: rows on the All Issues page are aggregated across
executions and don't carry an execution_id, so the backend has no pipeline or target context
to attach a narrower scope to. Org- and Account-scoped exemptions are not created here at all;
they're produced later by approving an existing exemption at a higher scope (via
harness_execute resource_type=security_exemption action=approve body={scope:'ORG'|'ACCOUNT'}),
which is outside the scope of this skill.
Instructions
Step 1 — Find out where the user is starting from
Ask the user, in plain language:
Which view are you in?
- The Vulnerabilities tab for a specific pipeline execution, or
- The All Issues page (the project-wide baseline view).
If you have the URL handy, just paste it — I'll pull out the org, project, and execution from it automatically.
You also need:
- The org and project, unless they're already in session defaults or you can read them from a pasted URL.
- For the Vulnerabilities tab path: the execution ID, or any Harness URL that contains one.
A pasted Harness UI URL is always the fastest route. The MCP url parameter auto-extracts every
identifier in the path, so the user does not have to type anything else. The shapes to recognise:
| URL the user pastes | What it tells you | Which path |
|---|---|---|
…/sto/executions/{executionId}/pipeline | The Vulnerabilities tab of one execution | Vulnerabilities path — extracts org_id, project_id, execution_id |
…/pipeline/orgs/{org}/projects/{project}/pipelines/{pipelineId}/executions/{executionId}/… | A pipeline execution detail page | Vulnerabilities path — also extracts pipeline_id |
…/sto/issues or …/sto/issues/{issueId} | The All Issues page | All Issues path — extracts org_id, project_id only |
If the user pastes a Vulnerabilities-tab URL, treat the request as the Vulnerabilities path no matter how they phrased it. If they paste an All Issues URL, do not ask for an execution ID — that view doesn't have one.
Step 2 — List the issues so the user can pick
Show a small preview first, not the whole list
Chat is a narrow surface — a 50-row table is unreadable, and the user usually only cares about a handful of issues. Start with a short preview, tell them the total, and let them ask for more or narrow the filter.
The default opening move:
- Ask
harness_listfor a small page (10 rows is a good default). - From the response, take
total— the total number of matching issues in the project / execution — and decide what to show:- If
total≤ 10, show every row. - If
total> 10, show the first 5 sorted by severity (Critical → High → Medium → Low), then say something like:Showing 5 of {total} matching issues, sorted by severity. Tell me how to narrow this — for example: "show 10 mediums", "only SAST", "search log4j", "show all highs" — or pick from the list below.
- If
- If the user asks for more or narrows the filter, re-call
harness_listwith the new filters or a larger page size. Do not paginate manually unless the user asks.
Vulnerabilities tab (per-execution)
harness_list
resource_type: "pipeline_security_issue"
org_id: <org>
project_id: <project>
filters:
execution_id: <execution_id> # REQUIRED
severity_codes: "Critical,High" # optional, user-driven
issue_types: "SCA,SAST" # optional
search: "<CVE or component>" # optional
include_exempted: false # hide rows that already have an exemption
page_size_existing: 10 # small preview — bump only on user request
page_size_new: 10
The response flattens the existing and new diff partitions into a single items[] and tags
each row with _partition. Each row exposes issue_id and targetVariantName (a display string
like "nodegoat:master"). It does not expose the raw target_id or pipeline_id — Step 3
covers how to look those up when the user picks a narrower scope.
All Issues page (baseline)
harness_list
resource_type: "security_issue"
org_id: <org>
project_id: <project>
filters:
severity_codes: "Critical,High"
issue_types: "SCA,SAST"
search: "<CVE or component>"
exemption_statuses: "None" # hide rows that already have an exemption
阅读完整来源 ↗