Registry Engine

Govern private package registry publish flows with registry_enforce.

What you will learn

• registry_get
• registry_plan
• registry_enforce

Prerequisites

• Mount PluginHost and merge MCP tools

Surface

What this feature does

Registry Engine encodes publish targets, auth requirements, and dry-run rules for npm/GitHub Packages style registries.

How to call it

Call these MCP tools through your AGS / tower-gov host — registry_get, registry_validate, registry_enforce, registry_plan.. Prefer scan/get before validate/diff, and enforce only when the change set is ready.

1. registry_get
2. registry_plan
3. Apply remediation
4. registry_enforce

{
  /* Example MCP call — fill args from schema_get / docs */
  "tool": "registry_get",
  "arguments": {}
}

What success looks like

registry_enforce ok

Policy matches live state

Common failure modes

Config enabled but requiredFiles missing

Enforce without validate

Plan ignored

Related reference

• Install
• Configuration