Critical-risk tools in Stellify
7 of the 50 tools in Stellify 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
-
broadcast_element_commandDestructivePush real-time UI updates via WebSocket. Use for SHOW/DISPLAY/DEMONSTRATE requests. Actions: update (modify element), create (ephemeral element), batch (multiple updates), dele...
-
delete_elementDestructiveDelete an element and all its children (CASCADE). Returns the count of deleted elements.
-
delete_fileDestructiveDelete a file from the project by UUID. This permanently removes the file and all its methods/statements. WARNING: This is destructive and cannot be undone. Make sure the file ...
-
delete_methodDestructiveDelete a method from a file by UUID. This permanently removes the method and all its code. Requires both the file UUID and method UUID.
-
delete_routeDestructiveDelete a route/page from the project by UUID. This permanently removes the route. WARNING: This is destructive and cannot be undone. Any elements attached to this route will be...
-
delete_settingDestructiveDelete a setting profile from the tenant
-
delete_statementDestructiveDelete a statement from a file by UUID. This permanently removes the statement (import, variable, ref, etc.).
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.