AI agents call delete_entity to permanently remove resources in O3de — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes entities from an O3DE level without the ability to undo the action through the tool itself. Deletion is irreversible and constitutes data destruction. While the blast radius is limited to a single level's entities rather than system-wide data, the irreversible nature and potential for cascading dependencies in a game engine justify 'high' severity.
From the tool's definition Tool name 'delete_entity' combined with description 'Delete an entity from the current O3DE level' explicitly performs an irreversible deletion operation.
Documented attack patterns abuse exactly the kind of access delete_entity gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and O3de, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_entity:
{
"version": "1",
"default": "deny",
"hide": [
"delete_entity"
]
}delete_entity disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete an entity from the current O3DE level. It is categorised as a Destructive tool in the O3de MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the O3de MCP server in PolicyLayer and add a rule for delete_entity: 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 O3de. Nothing to install.
delete_entity 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_entity 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_entity. 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_entity is provided by the O3de MCP server (nickschuetz/o3de-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from O3de, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
30 O3de tools catalogued and risk-classified — across an index of 43,000+ MCP servers.