Update an existing object/actor in the world\n\nExample output: {
AI agents use editor_update_object 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.
This tool creates or modifies data reversibly by updating existing objects/actors. It does not delete data (which would be Destructive) nor execute arbitrary code (which would be Execute).
From the tool's definition Tool name 'editor_update_object' and description states 'Update an existing object/actor in the world' — this modifies existing data/assets in the Unreal Editor.
Documented attack patterns abuse exactly the kind of access editor_update_object gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Unreal, and nothing reaches the server without passing your rules. This is the rule we recommend for editor_update_object:
{
"version": "1",
"default": "deny",
"tools": {
"editor_update_object": {
"limits": [
{
"counter": "editor_update_object_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}editor_update_object 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.
Free to start. No card required.
Update an existing object/actor in the world\n\nExample output: {. 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.
Register the Unreal 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. 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 server (runreal/unreal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 20 Unreal tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
20 Unreal tools catalogued and risk-classified — across an index of 42,500+ MCP servers.