This record as markdown: /tools/aadeshrao123-unreal-mcp/delete-actor.md
What delete_actor does on Unreal-MCP
AI agents call delete_actor to permanently remove resources in Unreal-MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_actor is rated Critical
This tool irreversibly removes actors (game objects) from an Unreal Engine level. Deletion cannot be undone programmatically by the tool itself, making this a destructive operation. While not as critical as data deletion in production systems, the loss of level design work represents significant irreversible harm.
From the tool's definition Tool name is 'delete_actor' and description states 'Delete an actor from the level by name.' The word 'delete' combined with the irreversible removal of game objects from a level indicates destructive action.
Attacks that exploit this kind of access
The rule that runs delete_actor 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 delete_actor, this is the rule to start with:
delete_actor is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Unreal-MCP, apply this rule, and every delete_actor call is checked against it from then on.
Questions about delete_actor
Delete an actor from the level by name. It is categorised as a Destructive tool in the Unreal-MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Unreal MCP server in PolicyLayer and add a rule for delete_actor: 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.
delete_actor is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_actor 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 delete_actor. 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.
delete_actor 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.
Across the catalogue