remove_niagara_emitter
Remove an emitter from a Niagara System by name.
This record as markdown: /tools/aadeshrao123-unreal-mcp/remove-niagara-emitter.md
What remove_niagara_emitter does on Unreal-MCP
AI agents call remove_niagara_emitter to permanently remove resources in Unreal-MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remove_niagara_emitter is rated Critical
Removing an emitter from a Niagara System deletes a VFX asset or component configuration that cannot be trivially restored without undo. While Unreal Engine editors typically support undo, the tool itself performs a destructive operation on game data/assets. The removal is irreversible at the tool's execution level (not reversible through the tool's parameters).
From the tool's definition Tool name 'remove_niagara_emitter' with description 'Remove an emitter from a Niagara System by name' — the verb 'remove' indicates irreversible deletion of a VFX component.
Attacks that exploit this kind of access
The rule that runs remove_niagara_emitter 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 remove_niagara_emitter, this is the rule to start with:
remove_niagara_emitter is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Unreal-MCP, apply this rule, and every remove_niagara_emitter call is checked against it from then on.
Questions about remove_niagara_emitter
Remove an emitter from a Niagara System by name. It is categorised as a Destructive tool in the Unreal-MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Unreal MCP server in PolicyLayer and add a rule for remove_niagara_emitter: 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.
remove_niagara_emitter is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_niagara_emitter 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 remove_niagara_emitter. 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.
remove_niagara_emitter 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