move_widget
Move a widget to a different parent panel.
This record as markdown: /tools/aadeshrao123-unreal-mcp/move-widget.md
What move_widget does on Unreal-MCP
AI agents use move_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.
Why move_widget is rated Medium
This tool creates or modifies data reversibly—it changes widget hierarchy and layout but does not execute arbitrary code, delete assets, or cause financial impact. The action can be undone (typical in UE5 editor with undo/redo). Severity is medium because misuse could disrupt a complex UI layout requiring manual repair, but the changes are non-destructive and localized to widget positioning.
From the tool's definition Tool name 'move_widget' and description 'Move a widget to a different parent panel' indicate the tool modifies the hierarchical structure of UI widgets by reassigning their parent container, which is a reversible structural change to the project.
Attacks that exploit this kind of access
The rule that runs move_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 move_widget, this is the rule to start with:
move_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Unreal-MCP, apply this rule, and every move_widget call is checked against it from then on.
Questions about move_widget
Move a widget to a different parent panel. 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 move_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.
move_widget 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 move_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.
Set action: deny in the PolicyLayer policy for move_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.
move_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.
More on Unreal, and thousands of servers like it.
This server
Across the catalogue