This record as markdown: /tools/jjpxdev-unreal-mcp/rename-asset.md
What rename_asset does on Unreal
AI agents use rename_asset to create or update resources in Unreal, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unreal environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
source_path | string | Yes | Current asset path |
destination_path | string | Yes | New asset path |
Parameters from the server's own tool schema.
Why rename_asset is rated Medium
Renaming or moving an asset is a reversible data modification operation. It changes asset properties and filesystem/catalog position but does not delete, execute code, or commit financial actions. This falls squarely into the Write category.
From the tool's definition rename_asset - Rename or move an asset. Modifies asset metadata/location without deleting or destroying the asset itself.
Risk signalsAccepts file system path (source_path)
Attacks that exploit this kind of access
The rule that runs rename_asset safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unreal, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rename_asset, this is the rule to start with:
rename_asset 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, apply this rule, and every rename_asset call is checked against it from then on.
Questions about rename_asset
Rename or move an asset. It is categorised as a Write tool in the Unreal MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
rename_asset accepts 2 parameters: source_path, destination_path. Required: source_path, destination_path. The full parameter table on this page comes from the server's own tool schema.
Register the Unreal MCP server in PolicyLayer and add a rule for rename_asset: 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. Nothing to install.
rename_asset 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_asset 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_asset. 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_asset is provided by the Unreal MCP server (@jjpxdev/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