compile_statetree

What compile_statetree does on Unreal-MCP

AI agents invoke compile_statetree to trigger actions in Unreal-MCP. 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 compile_statetree is rated High

Compiling a StateTree is an Execute-class action because it triggers external compilation operations within Unreal Engine 5 that generate code and process assets. While compilation itself is reversible (not Destructive), it is fundamentally an operation that runs compiler code whose side effects (generated files, temporary artifacts, editor state changes) depend on the arguments provided.

From the tool's definition Tool description: 'Compile a StateTree and return errors/warnings.' Compilation is an execute operation that triggers the Unreal Engine compiler to process StateTree assets, which involves code generation and asset processing whose effects depend on what…

The rule that runs compile_statetree safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Unreal-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For compile_statetree, this is the rule to start with:

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

Questions about compile_statetree