create-policy
Create OPA governance policies for Harness via MCP. Define policies that enforce compliance rules on pipelines, services, environments, feature flags, artifacts, code repositories, templates, SBOM, security tests, Terraform, GitOps, connectors, secrets, and more. Use when asked to create, write, fix, or explain an OPA policy, Rego rule, deny rule, governance policy, compliance rule, or policy-as-code for any Harness entity. Trigger phrases: create policy, OPA policy, governance policy, compliance rule, rego policy, deny rule, enforce policy, security policy, supply chain governance.
- License 许可
- Apache-2.0
- 最近更新
- 2026-06-06
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- create-policy
- license
- Apache-2.0
- metadata
- { "author": "Harness", "version": "1.0.0", "mcp-server": "harness-mcp-v2" }
- description
- Create OPA governance policies for Harness via MCP. Define policies that enforce compliance rules on pipelines, services, environments, feature flags, artifacts, code repositories, templates, SBOM, security tests, Terraform, GitOps, connectors, secrets, and more. Use when asked to create, write, fix, or explain an OPA policy, Rego rule, deny rule, governance policy, compliance rule, or policy-as-code for any Harness entity. Trigger phrases: create policy, OPA policy, governance policy, compliance rule, rego policy, deny rule, enforce policy, security policy, supply chain governance.
- compatibility
- Requires Harness MCP v2 server (harness-mcp-v2)
02 资源文件 18
- 参考文档references/advanced-patterns.md17.7 KB
- 参考文档references/entity-code-repository.md4.2 KB
- 参考文档references/entity-connector.md6.4 KB
- 参考文档references/entity-database.md4.9 KB
- 参考文档references/entity-feature-flag.md11.8 KB
- 参考文档references/entity-gitops.md6.6 KB
- 参考文档references/entity-override.md1.8 KB
- 参考文档references/entity-pipeline.md37.2 KB
- 参考文档references/entity-sbom.md6.5 KB
- 参考文档references/entity-secret.md5.2 KB
- 参考文档references/entity-security-tests.md7.9 KB
- 参考文档references/entity-service-env-infra.md5.4 KB
- 参考文档references/entity-template.md3.0 KB
- 参考文档references/entity-terraform.md24.8 KB
- 参考文档references/entity-upstream-firewall.md2.7 KB
- 参考文档references/entity-variable.md1.5 KB
- 参考文档references/quality-tests.md5.8 KB
- 参考文档references/rego-writing-guide.md8.4 KB
03 SKILL.md 正文
Create Policy
Create OPA governance policies for Harness Software Supply Chain Assurance (SCS) via MCP.
Instructions
Step 1: Identify Policy Requirements
Determine what the policy should enforce:
- What entity type is the policy targeting? (pipeline, service, environment, feature flag, etc.)
- What is the enforcement action (warn, deny)?
- What scope should the policy apply to?
- What action triggers the policy? (onrun, onsave, onstep, etc.)
For writing Rego policies, consult references/rego-writing-guide.md for the complete Rego writing rules, entity types, package names, and common patterns. For entity-specific schemas and examples, see the entity reference files listed in that guide.
Step 2: Create the Policy
Call MCP tool: harness_create
Parameters:
resource_type: "policy"
org_id: "<organization>"
project_id: "<project>"
body: <policy definition>
OPA policies are managed under the governance toolset — resource_type: "policy" supports full CRUD (list, get, create, update, delete).
Step 3: Verify Compliance Results
After a policy is created, check compliance status on artifacts or repositories:
Call MCP tool: harness_list
Parameters:
resource_type: "scs_compliance_result"
org_id: "<organization>"
project_id: "<project>"
Common Policy Patterns
Require SBOM Generation
Enforce that all artifacts have an SBOM before deployment:
package harness.artifact
deny[msg] {
not input.artifact.sbom
msg := "Artifact must have an SBOM before deployment"
}
Block Critical Vulnerabilities
Deny deployment of artifacts with critical CVEs:
package harness.artifact
deny[msg] {
vuln := input.artifact.vulnerabilities[_]
vuln.severity == "CRITICAL"
msg := sprintf("Critical vulnerability %s found in artifact", [vuln.cve_id])
}
Enforce Approved Base Images
Restrict container images to approved base images:
package harness.artifact
approved_bases := {"alpine", "distroless", "ubuntu"}
deny[msg] {
not approved_bases[input.artifact.base_image]
msg := sprintf("Base image '%s' is not in the approved list", [input.artifact.base_image])
}
Require Signed Artifacts
Enforce artifact signing before deployment:
package harness.artifact
deny[msg] {
not input.artifact.signed
msg := "Artifact must be signed before deployment"
}
Related Resource Types
| Resource Type | Operations | Description |
|---|---|---|
policy |
list, get, create, update, delete | OPA governance policies (governance toolset) |
policy_set |
list, get, create, update, delete | Group policies with enforcement actions |
policy_evaluation |
list, get | View policy evaluation results |
scs_compliance_result |
list | Check SCS policy compliance status |
artifact_security |
list, get | View artifact security posture |
code_repo_security |
list, get | View repository security posture |
scs_chain_of_custody |
get | Verify artifact provenance |
Rego Policy Reference Files
For writing Rego policies for any Harness entity, consult these reference files:
- Rego writing guide and rules — Entity types, package names, Rego patterns, quality checklist
- Pipeline policies and schema — Pipeline input schema, step/stage nesting, walk patterns
- Feature Flag / FME policies — Feature flag, definition, FME environment, segment schemas
- Service, Environment, Infrastructure — Service, env, infra schemas and examples
- Security Tests policies — Security test output schema, severity/coverage checks
- SBOM policies — SBOM deny/allow list patterns with semver comparison
- Terraform and Workspace — Terraform plan, cost, state, workspace schemas
- GitOps Application — GitOps app schema, namespace/label/revision policies
- Code Repository — Code repo naming, visibility, branch policies
- Variable policies — Variable schema, role-based restrictions
- Override policies — Override schema, config file and variable protection
- Connector policies — Connector schema, type/auth/naming restrictions
- Secret policies — Secret schema, naming/type/provider restrictions
- Template policies — Template schema, approval/versioning/environment checks
- Database DevOps policies — SQL statement governance, DDL restrictions, transaction limits
- Upstream Firewall — Firewall package schema, CVE/license policies
- Advanced patterns — Exception handling, walk, scoped references, exemptions
Examples
- "Create a policy to block critical CVEs" -- Create OPA deny rule for critical severity
- "Enforce SBOM generation for all artifacts" -- Create policy requiring SBOM presence
- "Only allow approved base images" -- Create policy with allowed base image list
- "Require artifact signing before production" -- Create policy checking signature status
- "Require approval before production deployments" -- Pipeline policy with Approval stage check
- "Enforce disallowPipelineExecutor on approval steps" -- Pipeline walk-based step check
- "Block Terraform plans exceeding $100/month" -- Terraform plan cost policy
- "Require feature flag descriptions" -- FME feature flag onsave policy
- "Prevent GitOps deployments to kube-system" -- GitOps namespace restriction
- "Check which artifacts violate our policies" -- List scs_compliance_result
Performance Notes
- Validate Rego syntax before submitting. Common issues: missing package declaration, deny rules without msg return.
- Ensure the policy package name follows
package harness.<domain>convention. - Test policy logic mentally against expected inputs before creating.
Troubleshooting
Policy Not Enforcing
- Verify the policy was created successfully (list via
resource_type: "policy") - Policies must be attached to a
policy_setwith an enforcement action (warn/deny) before they fire - Check that the policy scope matches the target artifacts/repositories
- Use
scs_compliance_resultorpolicy_evaluationto verify the policy is being evaluated
Policy Syntax Errors
- OPA policies use Rego language -- validate syntax before submitting
- Package names should follow
package harness.<domain>convention - Deny rules must return a
msgstring explaining the violation
Limitations
- Policies apply within the project scope where they are created
- Attach policies to a
policy_setto activate enforcement
04 同仓库更多 Skills
verify-sign
Add an Artifact Verification (SscaArtifactVerification) step to an existing Harness pipeline to verify Cosign signatures on container or local-stage artifacts. Supports CI, Security, and CD Deploy (containerized step group). Supports Third-Party registries (Docker, ECR, GCR, GAR, ACR), Harness Artifact Registry (HAR), and Harness Local Stage artifacts. Only works with existing pipelines. Use when asked to verify signed artifacts, verify artifact signature, verify-sign, validate Cosign signature, or configure SscaArtifactVerification. Trigger phrases: verify sign, verify artifact, artifact verification, verify signature, verify-sign, SscaArtifactVerification, verify signed image, verify Cosign, HAR verification.
template-usage
Track Harness template dependencies, usage, and adoption via MCP v2 tools. Find which pipelines or other templates reference a given template, analyze update impact, identify unused templates, and compare version adoption. Use when asked about template usage, template references, template dependencies, impact analysis before updating a template, finding unused templates, or tracking template adoption across projects. Trigger phrases: template usage, who uses template, template references, template dependencies, template impact, unused templates, template adoption. Do NOT use for creating or updating templates (use create-template instead).
sign-artifact
Add an Artifact Signing (SscaArtifactSigning) step to an existing Harness pipeline to Cosign-sign container or local-stage artifacts with keyless, key-based, or Vault signing. Supports Third-Party registries (Docker, ECR, GCR, GAR, ACR), Harness Artifact Registry (HAR), and Harness Local Stage artifacts. Place after image build/push; optionally upload .sig to the registry. Only works with existing pipelines. Use when asked to sign artifacts, add artifact signing, Cosign sign image, attach signature to registry, or configure SscaArtifactSigning. Trigger phrases: sign artifact, artifact signing, sign image, Cosign sign, add signing step, SscaArtifactSigning, attach signature, sign container image, HAR signing.
sei-analytics
Advanced engineering analytics via Harness Software Engineering Insights (SEI) MCP. Configure sprint velocity and estimation accuracy tracking, engineering investment allocation breakdowns, sprint planning with capacity forecasts, and release readiness assessments. Use when asked about sprint analytics, investment allocation, sprint planning, capacity forecasting, or release readiness. Do NOT use for DORA metrics (use dora-metrics instead). Trigger phrases: sprint velocity, sprint analytics, investment allocation, capacity planning, sprint forecast, release readiness, engineering productivity, estimation accuracy, sprint planning, scope creep, code quality trends.
security-report
Generate security compliance reports using Harness SCS and STO via MCP. Analyze vulnerabilities, SBOMs, and manage exemptions. Use when user says "security report", "vulnerabilities", "SBOM", "security scan", "compliance check", or asks about application security.
scorecard-review
Review service maturity scorecards and compliance using Harness IDP via MCP. Check production readiness, security, and documentation scores. Use when user says "scorecard", "service maturity", "production readiness", "compliance score", or asks about service health scores.