clear_niagara_module_input
A destructive tool on the Unreal- MCP server.
This record as markdown: /tools/aadeshrao123-unreal-mcp/clear-niagara-module-input.md
What clear_niagara_module_input does on Unreal-MCP
AI agents call clear_niagara_module_input 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 clear_niagara_module_input is rated Critical
The word 'clear' typically indicates an irreversible removal operation. In the context of Niagara (Unreal Engine's VFX system), clearing a module input would remove configured parameters, which may not be easily undone. However, the empty description significantly reduces certainty — it could be a reset/write operation rather than a true destructive one.
From the tool's definition Tool name 'clear_niagara_module_input' — 'clear' implies removal/deletion of input data on a Niagara VFX module. Description is empty, lowering confidence.
Attacks that exploit this kind of access
The rule that runs clear_niagara_module_input 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 clear_niagara_module_input, this is the rule to start with:
clear_niagara_module_input 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 clear_niagara_module_input call is checked against it from then on.
Questions about clear_niagara_module_input
clear_niagara_module_input is a destructive tool on the Unreal MCP server. 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 clear_niagara_module_input: 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.
clear_niagara_module_input 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 clear_niagara_module_input 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 clear_niagara_module_input. 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.
clear_niagara_module_input 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