compile_niagara_system
Compile a Niagara System and report any errors.
This record as markdown: /tools/aadeshrao123-unreal-mcp/compile-niagara-system.md
What compile_niagara_system does on Unreal-MCP
AI agents invoke compile_niagara_system 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_niagara_system is rated High
Compilation is an Execute action: it runs a build process within Unreal Engine that transforms VFX system definitions into executable bytecode or intermediate representations. While not destructive (reversible; can recompile), it is not a simple read/write/query operation.
From the tool's definition The tool 'compile_niagara_system' triggers compilation—a code generation and build operation whose effects depend on the system being compiled and the state of the project.
Attacks that exploit this kind of access
The rule that runs compile_niagara_system 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_niagara_system, this is the rule to start with:
compile_niagara_system 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-MCP, apply this rule, and every compile_niagara_system call is checked against it from then on.
Questions about compile_niagara_system
Compile a Niagara System and report any errors. It is categorised as a Execute tool in the Unreal-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Unreal MCP server in PolicyLayer and add a rule for compile_niagara_system: 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-MCP. Nothing to install.
compile_niagara_system 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 compile_niagara_system 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 compile_niagara_system. 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.
compile_niagara_system is provided by the Unreal MCP server (aadeshrao123/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