High-risk tools in Ue
2 of the 20 tools in Ue 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
-
flowExecute 4/5Run or inspect named flows defined in ue-mcp.yml. Config is reloaded on every call — no restart needed. Actions: - run: Execute a flow. Params: flowName, skip?, params?, rollba...
-
projectExecute 5/5Project status, config INI files, and C++ source inspection. Actions: - get_status: Check server mode and editor connection - set_project: Switch project. Params: projectPath -...
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.
More on Ue
Enforce policy on Ue
One command generates a policy scaffold for every server in your MCP config.
npx -y @policylayer/intercept init