remove_niagara_renderer
Remove a renderer from an emitter by index.
This record as markdown: /tools/aadeshrao123-unreal-mcp/remove-niagara-renderer.md
What remove_niagara_renderer does on Unreal-MCP
AI agents call remove_niagara_renderer 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_renderer is rated Critical
Removing a renderer from a Niagara emitter deletes that renderer configuration from the emitter. This is an irreversible destructive action within the Unreal Engine editor context. The severity is high because misuse could corrupt or break VFX emitters/systems that depend on the renderer, requiring significant manual effort to restore.
From the tool's definition 'Remove a renderer from an emitter by index' — permanently removes a renderer component from a Niagara emitter, which is a destructive operation that cannot be trivially undone.
Attacks that exploit this kind of access
The rule that runs remove_niagara_renderer 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_renderer, this is the rule to start with:
remove_niagara_renderer 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_renderer call is checked against it from then on.
Questions about remove_niagara_renderer
Remove a renderer from an emitter by index. 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_renderer: 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_renderer 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_renderer 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_renderer. 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_renderer 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