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/google-drive/manifest.yaml

@@ -1,8 +1,8 @@
 id: google_drive
 name: Google Drive
-version: 1.0.0
+version: 1.1.0
 description: "Google Drive (Drive API v3) — manage shared drives (create/list/get/delete), track file changes (start page token + change lists), query Drive activity, search and read files, create folders and metadata, upload/replace/download file content, copy, move and delete files, manage permissions (list/create/update/delete) and work with Drive labels. Authenticates with a Google service account (JWT bearer flow with domain-wide delegation to impersonate a Workspace user). Runs on a remote engine. Requires the Python 'PyJWT' and 'cryptography' libraries on the engine host (pip install pyjwt cryptography)."
-changelog: "1.0.0 — Initial release: shared drive management, changes tracking, Drive activity queries, file search/get/create, content upload/replace/download, copy/move/delete, parents, permissions management, Drive labels, test connection."
+changelog: "1.1.0 — Declare the risk tier on the 12 commands that carried none: 6 safe_write, 6 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: shared drive management, changes tracking, Drive activity queries, file search/get/create, content upload/replace/download, copy/move/delete, parents, permissions management, Drive labels, test connection."
 category: productivity
 
 # Per-instance configuration. Authentication uses the Google service-account
@@ -29,6 +29,7 @@ commands:
   - id: drive_create
     name: google-drive-drive-create
     description: "Create a new shared drive."
+    risk: safe_write
     inputs_schema:
       properties:
         name: { type: string, description: "Name of the shared drive to create" }
@@ -63,6 +64,7 @@ commands:
   - id: drive_delete
     name: google-drive-drive-delete
     description: "Permanently delete a shared drive."
+    risk: destructive
     inputs_schema:
       properties:
         drive_id: { type: string, description: "ID of the shared drive to delete" }
@@ -141,6 +143,7 @@ commands:
   - id: file_create
     name: google-drive-file-create
     description: "Create a folder or an empty file (metadata only — use file-upload for content)."
+    risk: safe_write
     inputs_schema:
       properties:
         file_name: { type: string, description: "Name of the file or folder to create" }
@@ -153,6 +156,7 @@ commands:
   - id: file_upload
     name: google-drive-file-upload
     description: "Upload a new file with content (base64-encoded)."
+    risk: safe_write
     inputs_schema:
       properties:
         file_name: { type: string, description: "Name of the file to create" }
@@ -164,6 +168,7 @@ commands:
   - id: file_replace
     name: google-drive-file-replace
     description: "Replace an existing file's content (base64-encoded)."
+    risk: destructive
     inputs_schema:
       properties:
         file_id: { type: string, description: "ID of the file to update" }
@@ -184,6 +189,7 @@ commands:
   - id: file_copy
     name: google-drive-file-copy
     description: "Copy a file, optionally with a new title."
+    risk: safe_write
     inputs_schema:
       properties:
         file_id: { type: string, description: "ID of the file to copy" }
@@ -194,6 +200,7 @@ commands:
   - id: file_move
     name: google-drive-file-move
     description: "Move a file between folders (add one parent, remove another)."
+    risk: safe_write
     inputs_schema:
       properties:
         file_id: { type: string, description: "ID of the file to move" }
@@ -205,6 +212,7 @@ commands:
   - id: file_delete
     name: google-drive-file-delete
     description: "Delete a file — permanently, or move it to the trash with soft_delete."
+    risk: destructive
     inputs_schema:
       properties:
         file_id: { type: string, description: "ID of the file to delete" }
@@ -238,6 +246,7 @@ commands:
   - id: permission_create
     name: google-drive-permission-create
     description: "Grant a permission on a file or shared drive (share with a user, group, domain or anyone)."
+    risk: destructive
     inputs_schema:
       properties:
         file_id: { type: string, description: "ID of the file or shared drive" }
@@ -254,6 +263,7 @@ commands:
   - id: permission_update
     name: google-drive-permission-update
     description: "Update a permission's role or expiration time."
+    risk: destructive
     inputs_schema:
       properties:
         file_id: { type: string, description: "ID of the file or shared drive" }
@@ -266,6 +276,7 @@ commands:
   - id: permission_delete
     name: google-drive-permission-delete
     description: "Revoke a permission from a file or shared drive."
+    risk: destructive
     inputs_schema:
       properties:
         file_id: { type: string, description: "ID of the file or shared drive" }
@@ -295,6 +306,7 @@ commands:
   - id: modify_label
     name: google-drive-modify-label
     description: "Apply, update or remove a Drive label on a file."
+    risk: safe_write
     inputs_schema:
       properties:
         file_id: { type: string, description: "ID of the file" }