feat: declare a risk tier on every command in the catalog

467 of the 1592 commands carried no `risk:`. An unset risk is read as
destructive by the agent approval gate, so half the catalog's write side sat
behind the same prompt — and, in HarfangLab's case, 39 pure lookups did too.
A gate that stops everything stops being read as a signal, which is the
argument already made for the toolkit and for sentinelone (df27876).

The catalog is now 1027 read, 261 safe_write, 304 destructive, with nothing
defaulted. The line follows the one sentinelone drew: impact on the estate,
not reversibility — isolate-agent is reversible and is the canonical
destructive example.

  read        only queries; changes nothing outside Riposte
  safe_write  additive or reversible inside the tool's own case/enrichment
              plane: comments, tickets, tags, alert statuses, threat-intel
              records, sandbox submissions, collection jobs, outbound messages
  destructive changes the estate or weakens a control: containment, blocklists
              and allowlists, exclusions and detection rules, every delete,
              identity and credential operations, code on a host, generic
              API escape hatches

Three calls that were not obvious, and are now applied throughout:

- Undoing a containment is tiered like the containment it lifts. Un-isolating
  a host or un-banning an IP mid-incident is its own decision, not a return to
  a neutral state. The catalog contradicted itself here — crowdstrike's
  lift_containment was destructive while harfanglab's deisolate_from_threat
  was safe_write — so deisolate_from_threat and unquarantine_file are
  re-tiered to destructive, the only two existing tiers this pass changes.
- Retrieving a live secret is destructive: cyberark get_password, delinea
  get_secret, vault read_secret, beyondtrust get_credential. It is a GET, but
  the tier describes the stake, not the HTTP verb.
- Sending outward to humans stays safe_write — slack, teams, twilio, telegram,
  mail. Irreversible, but it is the collaboration plane, not the estate.

An object created but not yet referenced by a rule is safe_write; editing one
a rule already reads is destructive. That is why fortigate create_address and
panos create_custom_url_category are safe_write while update_address_group and
edit_custom_url_category are not.

The template and README never documented the field, which is how 467 commands
came to omit it. Both now carry the tier table and these rules, so the next
integration declares a tier instead of inheriting one.

111 packages get a MINOR bump and a changelog entry: an instance compares
versions to offer an update, so an unbumped manifest would leave the tiers
sitting in the catalog and never reaching the estates that need them.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

integrations/servicenow-cmdb/manifest.yaml

@@ -1,8 +1,8 @@
 id: servicenow_cmdb
 name: ServiceNow CMDB
-version: 1.0.0
+version: 1.1.0
 description: "ServiceNow CMDB (CMDB Instance API) — query configuration items by CI class, read a record with its attributes and inbound/outbound relations, create and update records with attributes and relations, and add or delete relations between CIs. Basic or OAuth 2.0 (password grant) authentication."
-changelog: "1.0.0 — Initial release: records list by class, record get by sys_id (attributes + relations), record create/update with attributes and discovery source, add/delete relations."
+changelog: "1.1.0 — Declare the risk tier on the 4 commands that carried none: 3 safe_write, 1 destructive. An unset risk is read as destructive by the agent approval gate, so the 3 that only annotate sat behind the same prompt as the ones that change the estate. | 1.0.0 — Initial release: records list by class, record get by sys_id (attributes + relations), record create/update with attributes and discovery source, add/delete relations."
 category: asset_management
 
 # Per-instance configuration. The base URL is the instance root, e.g.
@@ -80,6 +80,7 @@ commands:
   - id: create_record
     name: servicenow-cmdb-create-record
     description: "Create a CI record with attributes and optional inbound/outbound relations."
+    risk: safe_write
     inputs_schema:
       properties:
         class: { type: string, description: "CI class name to create the record in" }
@@ -95,6 +96,7 @@ commands:
   - id: update_record
     name: servicenow-cmdb-update-record
     description: "Update a CI record's attributes."
+    risk: safe_write
     inputs_schema:
       properties:
         class: { type: string, description: "CI class name of the record" }
@@ -109,6 +111,7 @@ commands:
   - id: add_relations
     name: servicenow-cmdb-add-relations
     description: "Add inbound and/or outbound relations to an existing CI record."
+    risk: safe_write
     inputs_schema:
       properties:
         class: { type: string, description: "CI class name of the record" }
@@ -124,6 +127,7 @@ commands:
   - id: delete_relation
     name: servicenow-cmdb-delete-relation
     description: "Delete a relation from a CI record by the relation's sys_id."
+    risk: destructive
     inputs_schema:
       properties:
         class: { type: string, description: "CI class name of the record" }