Compile a Blueprint asset and return compilation status.
AI agents invoke blueprint_compile to trigger actions in Uefn. 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.
Compiling a Blueprint is an Execute-category action because it triggers code compilation with external effects on the Unreal editor state and generated code. While not destructive in itself, compilation can fail, consume resources, or potentially expose unintended logic.
From the tool's definition The tool 'blueprint_compile' compiles a Blueprint asset, which is a code compilation operation in Unreal Engine. Compilation is an execution action that processes code/assets and produces executable output.
Documented attack patterns abuse exactly the kind of access blueprint_compile gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Uefn, and nothing reaches the server without passing your rules. This is the rule we recommend for blueprint_compile:
{
"version": "1",
"default": "deny",
"tools": {
"blueprint_compile": {
"limits": [
{
"counter": "blueprint_compile_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}blueprint_compile 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.
Free to start. No card required.
Compile a Blueprint asset and return compilation status. It is categorised as a Execute tool in the Uefn MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Uefn MCP server in PolicyLayer and add a rule for blueprint_compile: 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 Uefn. Nothing to install.
blueprint_compile 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 blueprint_compile 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 blueprint_compile. 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.
blueprint_compile is provided by the Uefn MCP server (quangdang46/uefn-verse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Uefn, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
143 Uefn tools catalogued and risk-classified — across an index of 43,000+ MCP servers.