High-risk tools in Openl
5 of the 41 tools in Openl 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
-
cancel_traceExecuteCancel ongoing trace execution for a project.
-
deploy_projectExecuteDeploy a project to production environment. Publishes rules to a deployment repository for runtime execution. Use production repository name (not ID) - e.g.,
-
redeploy_projectExecuteRedeploy an existing deployment with a new project version. Use this to update a deployment with a newer version of the project or rollback to a previous version.
-
start_project_testsExecuteStart project test execution. For design repositories the project is automatically opened if closed; for repository
-
start_traceExecuteStart trace execution for a table. Trace is asynchronous (returns 202 Accepted). For regular rules: provide inputJson with { params: {...}, runtimeContext?: {...} }. For test ta...
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.