delete_niagara_scratch_pad_module
Delete a scratch pad module from a Niagara System.
This record as markdown: /tools/aadeshrao123-unreal-mcp/delete-niagara-scratch-pad-module.md
What delete_niagara_scratch_pad_module does on Unreal-MCP
AI agents call delete_niagara_scratch_pad_module 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_scratch_pad_module is rated Critical
The tool performs an irreversible deletion operation on Niagara VFX system data. Even though it targets a 'scratch pad' (which may suggest temporary/non-essential data), deletion operations in creative tools like Unreal Engine are classified as Destructive because the action cannot be undone through normal tool usage and represents permanent loss of user work.
From the tool's definition Tool name contains 'delete' and description states 'Delete a scratch pad module from a Niagara System' — this irreversibly removes data from a game asset.
Attacks that exploit this kind of access
The rule that runs delete_niagara_scratch_pad_module 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_scratch_pad_module, this is the rule to start with:
delete_niagara_scratch_pad_module 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_scratch_pad_module call is checked against it from then on.
Questions about delete_niagara_scratch_pad_module
Delete a scratch pad module from a Niagara System. 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_scratch_pad_module: 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_scratch_pad_module 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_scratch_pad_module 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_scratch_pad_module. 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_scratch_pad_module 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