Critical-risk tools in ContextLayer
10 of the 62 tools in ContextLayer 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
-
delete_documentDestructiveDelete a document from the knowledge base. This permanently removes the document.
-
delete_positionDestructiveDelete a position permanently (admin only). Find by title or ID.
-
delete_projectDestructiveDelete a project permanently (admin only). Find by name or ID.
-
delete_taskDestructiveDelete a task permanently. The task and all its assignee links are removed.
-
delete_teamDestructiveDelete a team permanently (admin only). Find by name or ID.
-
delete_userDestructiveDelete (soft-delete) a user from your organization (admin/owner only).
-
remove_task_dependencyDestructiveRemove a dependency between tasks. This unblocks the task from the other task.
-
remove_team_memberDestructiveRemove a member from a team. Find the team by name or ID, and the user by name or email.
-
remove_user_from_orgDestructiveRemove a user from the current organization without deleting their account. Admin/owner only.
-
unassign_taskDestructiveRemove a user from a task's assignees.
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.