build_graph
Execute a BuildGraph XML script for CI/CD automation.
This record as markdown: /tools/jjpxdev-unreal-mcp/build-graph.md
What build_graph does on Unreal
AI agents invoke build_graph 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
target | object | Yes | BuildGraph target to execute |
script_path | string | Yes | Path to the BuildGraph XML script |
additional_args | array | — | Additional arguments |
Parameters from the server's own tool schema.
Why build_graph is rated High
BuildGraph scripts control compilation, packaging, and deployment workflows in Unreal Engine's build system. An AI agent with access to this tool could execute arbitrary build operations—compiling code, packaging builds, triggering deployments, or modifying artifacts—with unpredictable side effects depending on the provided XML script.
From the tool's definition 'Execute a BuildGraph XML script for CI/CD automation' indicates the tool runs external scripts (BuildGraph XML) that trigger CI/CD pipelines and automated build processes whose effects depend on the script content and configuration.
Attacks that exploit this kind of access
The rule that runs build_graph safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unreal, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For build_graph, this is the rule to start with:
build_graph 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Unreal, apply this rule, and every build_graph call is checked against it from then on.
Questions about build_graph
Execute a BuildGraph XML script for CI/CD automation. 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.
build_graph accepts 3 parameters: target, script_path, additional_args. Required: target, script_path. The full parameter table on this page comes from the server's own tool schema.
Register the Unreal MCP server in PolicyLayer and add a rule for build_graph: 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.
build_graph is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the build_graph 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.
Set action: deny in the PolicyLayer policy for build_graph. 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.
build_graph is provided by the Unreal MCP server (@jjpxdev/unreal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Unreal, and thousands of servers like it.
Across the catalogue