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/microsoft-sentinel/manifest.yaml

@@ -1,8 +1,8 @@
 id: microsoft_sentinel
 name: Microsoft Sentinel
-version: 1.0.0
+version: 1.1.0
 description: "Microsoft Sentinel (Azure Resource Manager API) — incident management (list/get/create/update/delete, comments, related alerts/entities), watchlists, threat indicators, and incident ingestion (get_incidents) with an OCSF mapper. Azure AD OAuth 2.0 client-credentials authentication. Stdlib-only, no extra Python dependencies."
-changelog: "1.0.0 — Initial release: incident CRUD + comments + related data, watchlist listing/upsert, threat indicator CRUD, and incident ingestion with an OCSF mapper."
+changelog: "1.1.0 — Declare the risk tier on the 8 commands that carried none: 6 safe_write, 2 destructive. An unset risk is read as destructive by the agent approval gate, so the 6 that only annotate sat behind the same prompt as the ones that change the estate. | 1.0.0 — Initial release: incident CRUD + comments + related data, watchlist listing/upsert, threat indicator CRUD, and incident ingestion with an OCSF mapper."
 category: siem
 
 # Per-instance configuration. Register an Azure AD application, grant it the
@@ -78,6 +78,7 @@ commands:
   - id: create_incident
     name: microsoft-sentinel-create-incident
     description: "Create an incident."
+    risk: safe_write
     inputs_schema:
       properties:
         title: { type: string, description: "Incident title" }
@@ -90,6 +91,7 @@ commands:
   - id: update_incident
     name: microsoft-sentinel-update-incident
     description: "Update an incident's title, status, severity, classification or owner."
+    risk: safe_write
     inputs_schema:
       properties:
         incident_id: { type: string, description: "Incident name/ID (GUID)" }
@@ -105,6 +107,7 @@ commands:
   - id: delete_incident
     name: microsoft-sentinel-delete-incident
     description: "Delete an incident."
+    risk: destructive
     inputs_schema:
       properties:
         incident_id: { type: string, description: "Incident name/ID (GUID)" }
@@ -113,6 +116,7 @@ commands:
   - id: add_comment
     name: microsoft-sentinel-add-comment
     description: "Add a comment to an incident."
+    risk: safe_write
     inputs_schema:
       properties:
         incident_id: { type: string, description: "Incident name/ID (GUID)" }
@@ -180,6 +184,7 @@ commands:
   - id: upsert_watchlist_item
     name: microsoft-sentinel-upsert-watchlist-item
     description: "Create or update a watchlist item (properties as a JSON object)."
+    risk: safe_write
     inputs_schema:
       properties:
         watchlist_alias: { type: string, description: "Watchlist alias" }
@@ -202,6 +207,7 @@ commands:
   - id: create_threat_indicator
     name: microsoft-sentinel-create-threat-indicator
     description: "Create a threat intelligence indicator."
+    risk: safe_write
     inputs_schema:
       properties:
         value: { type: string, description: "Indicator value" }
@@ -215,6 +221,7 @@ commands:
   - id: update_threat_indicator
     name: microsoft-sentinel-update-threat-indicator
     description: "Update a threat intelligence indicator (display name, confidence, expiry, threat types)."
+    risk: safe_write
     inputs_schema:
       properties:
         indicator_name: { type: string, description: "Indicator name (from list_threat_indicators)" }
@@ -227,6 +234,7 @@ commands:
   - id: delete_threat_indicator
     name: microsoft-sentinel-delete-threat-indicator
     description: "Delete a threat intelligence indicator by name."
+    risk: destructive
     inputs_schema:
       properties:
         indicator_name: { type: string, description: "Indicator name (from list_threat_indicators)" }