run_editor_utility_widget · Unreal MCP: Risk & Policy

WHAT IT DOES

What run_editor_utility_widget does on Unreal

AI agents invoke run_editor_utility_widget to trigger actions in Unreal. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why run_editor_utility_widget needs a policy

This tool executes arbitrary Editor Utility Widget code, which can manipulate the editor state, modify assets, execute Python scripts, and trigger side effects across the Unreal Engine environment. The execution is parameterized by asset path, meaning an AI agent could be tricked into running malicious or unintended widgets. This is a code execution primitive with potentially unbounded scope within the engine.

From the tool's definition Tool name 'run_editor_utility_widget' combined with description 'Run an Editor Utility Widget by asset path' indicates execution of arbitrary widget logic.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_editor_utility_widget Rate-limited

run_editor_utility_widget stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_editor_utility_widget": {
      "limits": [
        {
          "counter": "run_editor_utility_widget_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Unreal, so you can run agents against it safely.

FAQ

Questions about run_editor_utility_widget

What does the run_editor_utility_widget tool do? +

Run an Editor Utility Widget by asset path. It is categorised as a Execute tool in the Unreal MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_editor_utility_widget? +

Register the Unreal MCP server in PolicyLayer and add a rule for run_editor_utility_widget: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Unreal. Nothing to install.

What risk level is run_editor_utility_widget? +

run_editor_utility_widget is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_editor_utility_widget? +

Yes. Add a rate_limit block to the run_editor_utility_widget rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block run_editor_utility_widget completely? +

Set action: deny in the PolicyLayer policy for run_editor_utility_widget. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides run_editor_utility_widget? +

run_editor_utility_widget is provided by the Unreal MCP server (sam-david/unreal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.