Critical-risk tools in LocalAnt
10 of the 216 tools in LocalAnt 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
-
adb_clear_logcatDestructiveClear the logcat buffer.
-
adb_uninstallDestructiveUninstall an app by package. Requires approval (risk 3).
-
fs_delete_file_with_approvalDestructiveDelete a file (a backup is kept). Requires approval.
-
git_resetDestructivegit reset --soft|--mixed|--hard. Hard reset is destructive (risk 4).
-
git_reset_hardDestructivegit reset --hard (DESTRUCTIVE: discards commits and working-tree changes).
-
git_restore_fileDestructiveDiscard changes to a file (git restore).
-
mcp_server_unregisterDestructiveRemove a registered downstream MCP server.
-
secret_removeDestructiveRemove a stored secret by name (risk 4).
-
shell_remove_allowed_commandDestructiveRemove a command prefix from the allowlist.
-
skill_uninstallDestructiveDelete a user-installed skill (bundled skills cannot be removed).
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.