rename_widget

Rename a widget (fixes up Blueprint variable tracking if bIsVariable).

SERVERUnreal-MCP SOURCEaadeshrao123/unreal-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/aadeshrao123-unreal-mcp/rename-widget.md

WHAT IT DOES

What rename_widget does on Unreal-MCP

AI agents use rename_widget 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.

RISK

Why rename_widget is rated Medium

This tool modifies existing widget names and their associated Blueprint variable tracking, which is a reversible metadata/naming change. It does not delete data (Destructive), execute arbitrary code (Execute), or move money (Financial). It's a Write operation because it changes the state of a widget definition, affecting both the widget name and related Blueprint variable references.

From the tool's definition Rename a widget (fixes up Blueprint variable tracking if bIsVariable).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs rename_widget 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_widget, this is the rule to start with:

rename_widget Rate-limited

rename_widget 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_widget": {
      "limits": [
        {
          "counter": "rename_widget_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 Unreal-MCP, apply this rule, and every rename_widget call is checked against it from then on.

FAQ

Questions about rename_widget

What does the rename_widget tool do? +

Rename a widget (fixes up Blueprint variable tracking if bIsVariable). 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.

How do I enforce a policy on rename_widget? +

Register the Unreal MCP server in PolicyLayer and add a rule for rename_widget: 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 rename_widget? +

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

Can I rate-limit rename_widget? +

Yes. Add a rate_limit block to the rename_widget 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_widget completely? +

Set action: deny in the PolicyLayer policy for rename_widget. 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_widget? +

rename_widget 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.

KEEP EXPLORING

More on Unreal, and thousands of servers like it.

This server

All 286 Unreal tools →

Across the catalogue

The MCP Attack Database →

Guides

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