This record as markdown: /tools/aadeshrao123-unreal-mcp/delete-niagara-system.md
What delete_niagara_system does on Unreal-MCP
AI agents call delete_niagara_system 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 delete_niagara_system is rated Critical
Deleting a Niagara System asset is an irreversible operation that permanently removes data from the Unreal Engine project. This cannot be undone programmatically and results in loss of VFX work.
From the tool's definition Tool name is 'delete_niagara_system' and description states 'Delete a Niagara System asset.' The use of 'Delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs delete_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 delete_niagara_system, this is the rule to start with:
delete_niagara_system 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 delete_niagara_system call is checked against it from then on.
Questions about delete_niagara_system
Delete a Niagara System asset. 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 delete_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.
delete_niagara_system 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 delete_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 delete_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.
delete_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