High-risk tools in LexQ
7 of the 63 tools in LexQ are classified as high 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 high risk
-
lexq_ab_test_startExecuteStart an A/B test on a policy group. Requires a challenger version ID and traffic rate.
-
lexq_ab_test_stopExecuteStop a running A/B test. All traffic is restored to the control (current) version.
-
lexq_deploy_liveExecuteDeploy an ACTIVE (published) version to live traffic. Takes effect immediately. Undefined facts do not block deployment (INV-4); use lexq_facts_unregistered to review what the v...
-
lexq_deploy_publishExecutePublish a DRAFT version (DRAFT → ACTIVE). Locks the version from further edits. Must have at least one rule. Undefined facts referenced by rules do not block publishing (INV-4);...
-
lexq_deploy_undeployExecuteRemove the live version from traffic. The version stays ACTIVE but no longer serves requests.
-
lexq_logs_actionExecuteProcess a single failure log: RETRY (re-execute with original payload), RESOLVE (mark as manually fixed), or IGNORE (skip intentionally).
-
lexq_webhook_subscriptions_testExecuteSend a test event to verify webhook connectivity. Returns the HTTP status code and success/failure message.
Attacks that target this class
High-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.