Critical Risk →

editor_delete_object

Delete an object/actor from the world\n\nExample output: {

How to control editor_delete_object ↓

AI agents call editor_delete_object to permanently remove resources in Unreal — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

This tool permanently removes objects or actors from the Unreal Engine world, which cannot be undone programmatically by the tool itself. While undo may exist in the editor UI, the tool's function is fundamentally destructive. Severity is high because an AI agent misusing this could delete critical scene elements, assets, or project structure in an active Unreal project, causing significant loss of work.

From the tool's definition Tool name is 'editor_delete_object' with description 'Delete an object/actor from the world'. The verb 'delete' combined with the action of removing objects/actors from a Unreal Editor world indicates irreversible data destruction.

Documented attack patterns abuse exactly the kind of access editor_delete_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_delete_object:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "editor_delete_object"
  ]
}

editor_delete_object disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Unreal — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the editor_delete_object tool do? +

Delete an object/actor from the world\n\nExample output: {. It is categorised as a Destructive tool in the Unreal MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on editor_delete_object? +

Register the Unreal MCP server in PolicyLayer and add a rule for editor_delete_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.

What risk level is editor_delete_object? +

editor_delete_object is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit editor_delete_object? +

Yes. Add a rate_limit block to the editor_delete_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.

How do I block editor_delete_object completely? +

Set action: deny in the PolicyLayer policy for editor_delete_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.

What MCP server provides editor_delete_object? +

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

Enforce policy on every Unreal tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.