Critical-risk tools in GitHub
6 of the 256 tools in GitHub are classified as critical risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at critical risk
-
actionDestructiveAction to perform: ignore, watch, or delete the repository notification subscription. (string, required)
-
delete_fileDestructiveDelete file
-
forceDestructiveForce removal even if worktree is dirty or locked (optional, default: false) (boolean, optional)
-
git_resetDestructiveGit reset
-
git_worktree_removeDestructiveGit worktree remove
-
updated_fieldDestructiveObject consisting of the ID of the project field to update and the new value for the field. To clear the field, set value to null. Example: {"id": 123456, "value": "New Value"}....
Attacks that target this class
Critical-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.