High Risk →

control_editor

Start/stop PIE, control viewport camera, run console commands, take screenshots, simulate input.

Accepts file system path (filename); Accepts freeform code/query input (command); High parameter count (36 properties)

Part of the Unreal Engine MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

unreal-engine-mcp-server Execute Risk 5/5

AI agents invoke control_editor to trigger processes or run actions in Unreal Engine. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

control_editor can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

io-github-chir24-unreal-engine-mcp.yaml
tools:
  control_editor:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Unreal Engine policy for all 35 tools.

Tool Name control_editor
Category Execute
Risk Level High

View all 35 tools →

Agents calling execute-class tools like control_editor have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

control_editor is one of the high-risk operations in Unreal Engine. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the control_editor tool do? +

Start/stop PIE, control viewport camera, run console commands, take screenshots, simulate input.. It is categorised as a Execute tool in the Unreal Engine MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on control_editor? +

Add a rule in your Intercept YAML policy under the tools section for control_editor. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Unreal Engine MCP server.

What risk level is control_editor? +

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

Can I rate-limit control_editor? +

Yes. Add a rate_limit block to the control_editor rule in your Intercept 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 control_editor completely? +

Set action: deny in the Intercept policy for control_editor. 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 control_editor? +

control_editor is provided by the Unreal Engine MCP server (unreal-engine-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Unreal Engine

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.