Update an existing object/actor in the world Example output: {'success': true, 'actor_name': 'StaticMeshActor_1', 'actor_label': 'UpdatedCube', 'class': 'StaticMeshActor', 'location': {'x': 150.0, 'y': 200.0, 'z': 50.0}, 'rotation': {'pitch': 0.0, 'yaw': 90.0, 'roll': 0.0}, 'scale': {'x': 2.0, 'y...
AI agents use editor_update_object to create or update resources in Unreal Mcp Ue4 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unreal Mcp Ue4 environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
scale | object | — | New scale multipliers |
location | object | — | New world position coordinates |
new_name | string | — | New name/label for the actor |
rotation | object | — | New rotation in degrees |
actor_name | string | Yes | Name or label of the actor to update |
properties | object | — | Additional actor properties to update. For StaticMeshActor: use 'StaticMesh' for mesh path, 'Material' for single material path, or 'Materials' for array of mat |
Parameters from the server's own tool schema.
An AI agent can call editor_update_object faster than any human can review — one bad instruction and it creates or modifies resources in Unreal Mcp Ue4 by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (15 properties)
Attacks that exploit this kind of access
Update an existing object/actor in the world Example output: {'success': true, 'actor_name': 'StaticMeshActor_1', 'actor_label': 'UpdatedCube', 'class': 'StaticMeshActor', 'location': {'x': 150.0, 'y': 200.0, 'z': 50.0}, 'rotation': {'pitch': 0.0, 'yaw': 90.0, 'roll': 0.0}, 'scale': {'x': 2.0, 'y': 2.0, 'z': 2.0}} Returns updated actor details with new transform values. It is categorised as a Write tool in the Unreal Mcp Ue4 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
editor_update_object accepts 6 parameters: scale, location, new_name, rotation, actor_name, properties. Required: actor_name. The full parameter table on this page comes from the server's own tool schema.
Register the Unreal Mcp Ue4 MCP server in PolicyLayer and add a rule for editor_update_object: 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 Ue4. Nothing to install.
editor_update_object 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 editor_update_object 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 editor_update_object. 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.
editor_update_object is provided by the Unreal Mcp Ue4 MCP server (unreal-mcp-ue4). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.