rename_niagara_scratch_pad_module
Rename a scratch pad module on a Niagara System.
This record as markdown: /tools/aadeshrao123-unreal-mcp/rename-niagara-scratch-pad-module.md
What rename_niagara_scratch_pad_module does on Unreal-MCP
AI agents use rename_niagara_scratch_pad_module 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 rename_niagara_scratch_pad_module is rated Medium
Renaming is a reversible modification operation that changes asset metadata but preserves the asset and its functional content. This is characteristic of Write operations. The severity is medium because renaming could cause confusion if done incorrectly (breaking references or conventions), but the action is easily reversible and does not cause data loss or execute arbitrary code.
From the tool's definition Tool name contains 'rename' and description states 'Rename a scratch pad module on a Niagara System', which modifies metadata/naming of an existing asset without deleting or destructively altering the underlying data.
Attacks that exploit this kind of access
The rule that runs rename_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 rename_niagara_scratch_pad_module, this is the rule to start with:
rename_niagara_scratch_pad_module 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 rename_niagara_scratch_pad_module call is checked against it from then on.
Questions about rename_niagara_scratch_pad_module
Rename a scratch pad module on a Niagara System. 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 rename_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.
rename_niagara_scratch_pad_module 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 rename_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 rename_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.
rename_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.
This server
Across the catalogue