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-graph-files/manifest.yaml

@@ -1,8 +1,8 @@
 id: microsoft_graph_files
 name: Microsoft Graph Files
-version: 1.0.0
+version: 1.1.0
 description: "Microsoft Graph file management for O365 (OneDrive / SharePoint / Teams) — browse sites, drives and content, create folders, upload/replace/download files, manage site permissions, read SharePoint lists, and edit Excel worksheets. App-only authentication (client credentials)."
-changelog: "1.0.0 — Initial release: SharePoint sites/drives/content browsing, folder creation, file delete/upload/replace/download (via URL or base64), site permission management (list/create/update/delete), SharePoint list reading (lists/items/get-item), and Excel worksheet editing (add-row/get-worksheet/update-cell). App-only client-credentials authentication."
+changelog: "1.1.0 — Declare the risk tier on the 9 commands that carried none: 4 safe_write, 5 destructive. An unset risk is read as destructive by the agent approval gate, so the 4 that only annotate sat behind the same prompt as the ones that change the estate. | 1.0.0 — Initial release: SharePoint sites/drives/content browsing, folder creation, file delete/upload/replace/download (via URL or base64), site permission management (list/create/update/delete), SharePoint list reading (lists/items/get-item), and Excel worksheet editing (add-row/get-worksheet/update-cell). App-only client-credentials authentication."
 category: productivity
 
 # Per-instance configuration. Uses app-only (client credentials) authentication
@@ -95,6 +95,7 @@ commands:
   - id: create_new_folder
     name: msgraph-create-new-folder
     description: "Create a folder under a parent item in a drive."
+    risk: safe_write
     inputs_schema:
       properties:
         object_type: { type: string, description: "drives, groups, sites or users" }
@@ -106,6 +107,7 @@ commands:
   - id: delete_file
     name: msgraph-delete-file
     description: "Delete a drive item (file or folder) by its ID."
+    risk: destructive
     inputs_schema:
       properties:
         object_type: { type: string, description: "drives, groups, sites or users" }
@@ -130,6 +132,7 @@ commands:
   - id: upload_new_file
     name: msgraph-upload-new-file
     description: "Upload a new file into a folder. Provide the content via content_base64 or source_url."
+    risk: safe_write
     inputs_schema:
       properties:
         object_type: { type: string, description: "drives, groups, sites or users" }
@@ -143,6 +146,7 @@ commands:
   - id: replace_existing_file
     name: msgraph-replace-existing-file
     description: "Replace the content of an existing file. Provide the new content via content_base64 or source_url."
+    risk: destructive
     inputs_schema:
       properties:
         object_type: { type: string, description: "drives, groups, sites or users" }
@@ -168,6 +172,7 @@ commands:
   - id: create_site_permissions
     name: msgraph-create-site-permissions
     description: "Grant an application permission (read/write/owner) on a site."
+    risk: destructive
     inputs_schema:
       properties:
         site_id: { type: string, description: "Site ID (or provide site_name)" }
@@ -180,6 +185,7 @@ commands:
   - id: update_site_permissions
     name: msgraph-update-site-permissions
     description: "Update the role of an existing site permission."
+    risk: destructive
     inputs_schema:
       properties:
         site_id: { type: string, description: "Site ID (or provide site_name)" }
@@ -191,6 +197,7 @@ commands:
   - id: delete_site_permissions
     name: msgraph-delete-site-permissions
     description: "Delete an application permission from a site."
+    risk: destructive
     inputs_schema:
       properties:
         site_id: { type: string, description: "Site ID (or provide site_name)" }
@@ -247,6 +254,7 @@ commands:
   - id: excel_add_row
     name: msgraph-excel-add-row
     description: "Append a row to an Excel worksheet. 'data' is a JSON object mapping column number (1-based) to value, e.g. {\"1\":\"foo\",\"2\":42}."
+    risk: safe_write
     inputs_schema:
       properties:
         object_type: { type: string, description: "drives, groups, sites or users" }
@@ -273,6 +281,7 @@ commands:
   - id: excel_update_cell
     name: msgraph-excel-update-cell
     description: "Overwrite a single Excel cell. 'column' may be a number or 'Col_2'."
+    risk: safe_write
     inputs_schema:
       properties:
         object_type: { type: string, description: "drives, groups, sites or users" }