delete_niagara_scratch_pad_module

Delete a scratch pad module from a Niagara System.

SERVERUnreal-MCP SOURCEaadeshrao123/unreal-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about delete_niagara_scratch_pad_module

What does the delete_niagara_scratch_pad_module tool do? +

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.

How do I enforce a policy on delete_niagara_scratch_pad_module? +

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.

What risk level is delete_niagara_scratch_pad_module? +

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.

Can I rate-limit delete_niagara_scratch_pad_module? +

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.

How do I block delete_niagara_scratch_pad_module completely? +

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.

What MCP server provides delete_niagara_scratch_pad_module? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Unreal's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.