apply_and_save_niagara_scratch_pad
Apply a scratch pad module's edit-copy AND save the asset (Apply & Save button).
This record as markdown: /tools/aadeshrao123-unreal-mcp/apply-and-save-niagara-scratch-pad.md
What apply_and_save_niagara_scratch_pad does on Unreal-MCP
AI agents use apply_and_save_niagara_scratch_pad to create or update resources in Unreal-MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unreal-MCP environment.
Why apply_and_save_niagara_scratch_pad is rated Medium
This tool modifies Niagara VFX assets by applying edits from a scratch pad and persisting them to disk. While 'save' suggests persistence, the operation is reversible (assets can be reverted, re-edited, or deleted), making it Write rather than Destructive. Severity is medium because unintended modifications to VFX assets could require rework but don't cause permanent data loss or external side effects.
From the tool's definition Tool name contains 'apply_and_save', description states 'Apply & Save button' - both indicate creation/modification of asset data. Affects Niagara VFX scratch pad modules which are reversible edits.
Attacks that exploit this kind of access
The rule that runs apply_and_save_niagara_scratch_pad 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 apply_and_save_niagara_scratch_pad, this is the rule to start with:
apply_and_save_niagara_scratch_pad stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Unreal-MCP, apply this rule, and every apply_and_save_niagara_scratch_pad call is checked against it from then on.
Questions about apply_and_save_niagara_scratch_pad
Apply a scratch pad module's edit-copy AND save the asset (Apply & Save button). It is categorised as a Write tool in the Unreal-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Unreal MCP server in PolicyLayer and add a rule for apply_and_save_niagara_scratch_pad: 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.
apply_and_save_niagara_scratch_pad is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the apply_and_save_niagara_scratch_pad 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 apply_and_save_niagara_scratch_pad. 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.
apply_and_save_niagara_scratch_pad 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.
This server
Across the catalogue