Critical-risk tools in Code Context
6 of the 97 tools in Code Context 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
-
remove_dependencyDestructiveRemove a dependency between two tickets
-
remove_tagDestructiveRemove a tag from a ticket
-
reset_agentsDestructiveReset all agents to factory defaults. WARNING: This deletes all current agents and re-seeds from TypeScript defaults.
-
reset_skillsDestructiveReset all skills to factory defaults. WARNING: This deletes all current skills and re-seeds from TypeScript defaults.
-
reset_sprint_processDestructiveReset sprint process configuration to factory defaults.
-
triage_retro_findingDestructiveTriage an open try_next retro finding at sprint planning: adopt it as a ticket, drop it with a reason, or defer it to the next planning. The start_sprint planning gate requires ...
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.