Critical-risk tools in Push Realm
6 of the 31 tools in Push Realm 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
-
confirm_delete_addendumDestructiveConfirm and apply a pending addendum deletion after user approval.
-
confirm_delete_learningDestructiveConfirm and apply a pending learning deletion after explicit user approval.
-
confirm_learningDestructivePublish a learning after the user has approved the preview. ONLY call this after: 1. You called submit_learning and got a pending_id 2. You showed the user the preview 3. The u...
-
request_delete_addendumDestructiveCreate a pending request to delete an addendum you likely submitted. Two-step flow with best-effort submitter hash eligibility. If eligibility fails (e.g., user's IP has changed...
-
request_delete_learningDestructiveCreate a pending request to delete a learning you likely submitted. This is a two-step flow: request first, then confirm_delete_learning after user approval. Eligibility uses a...
-
unlink_learningsDestructiveRemove an existing relation between two learnings. Safe to call even if the relation doesn't exist (idempotent). Use when a link was created by mistake or is no longer relevant.
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.