control_niagara_effect
Control a Niagara effect actor in the level.
This record as markdown: /tools/aadeshrao123-unreal-mcp/control-niagara-effect.md
What control_niagara_effect does on Unreal-MCP
AI agents invoke control_niagara_effect 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 control_niagara_effect is rated High
Controlling a Niagara effect actor involves triggering or manipulating a runtime VFX system in the level, which constitutes executing an external operation whose effects depend on arguments. It is not a simple read, nor is it clearly destructive or financial. The blast radius is medium since misuse could disrupt level state but is generally reversible.
From the tool's definition 'Control a Niagara effect actor in the level' — triggers/controls an external operation (a Niagara VFX system) running within the Unreal Engine editor environment
Attacks that exploit this kind of access
The rule that runs control_niagara_effect 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 control_niagara_effect, this is the rule to start with:
control_niagara_effect 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 control_niagara_effect call is checked against it from then on.
Questions about control_niagara_effect
Control a Niagara effect actor in the level. 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 control_niagara_effect: 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.
control_niagara_effect 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 control_niagara_effect 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 control_niagara_effect. 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.
control_niagara_effect 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