rename_asset

A write tool on the Uefn MCP server.

SERVERUefn SOURCEquangdang46/uefn-verse-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/quangdang46-uefn-verse-mcp/rename-asset.md

WHAT IT DOES

What rename_asset does on Uefn

AI agents use rename_asset to create or update resources in Uefn, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Uefn environment.

RISK

Why rename_asset is rated Medium

Renaming assets in a game editor is a write operation—it modifies metadata reversibly. While not destructive (the original asset still exists under a new name), it can have broad side effects on project references and workflows. High severity because an AI agent could systematically rename critical assets, breaking references or creating confusion in a live UEFN project.

From the tool's definition Tool name 'rename_asset' indicates modification of asset metadata. In Unreal Editor for Fortnite, renaming assets changes their identity and references throughout a project, making this a reversible write operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs rename_asset safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Uefn, 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 Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rename_asset": {
      "limits": [
        {
          "counter": "rename_asset_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Uefn, apply this rule, and every rename_asset call is checked against it from then on.

FAQ

Questions about rename_asset

What does the rename_asset tool do? +

rename_asset is a write tool on the Uefn MCP server. It is categorised as a Write tool in the Uefn MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on rename_asset? +

Register the Uefn 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 Uefn. Nothing to install.

What risk level is rename_asset? +

rename_asset is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit rename_asset? +

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.

How do I block rename_asset completely? +

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.

What MCP server provides rename_asset? +

rename_asset is provided by the Uefn MCP server (quangdang46/uefn-verse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Uefn, and thousands of servers like it.

This server

All 143 Uefn tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →