Duplicate an entity (and its children) in the current O3DE level.
AI agents use duplicate_entity to create or update resources in O3de — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your O3de environment.
Duplicating entities is a reversible modification operation that creates new data structures within the O3DE level editor. While it modifies the level state, it does not delete, destroy, or irreversibly alter data (hence not Destructive), nor does it execute arbitrary code or external operations (hence not Execute). It is a Create/Write action that can be undone in typical editor workflows.
From the tool's definition Tool is named 'duplicate_entity' and described as 'Duplicate an entity (and its children) in the current O3DE level.' The action creates new entity instances by copying existing ones.
Documented attack patterns abuse exactly the kind of access duplicate_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 duplicate_entity:
{
"version": "1",
"default": "deny",
"tools": {
"duplicate_entity": {
"limits": [
{
"counter": "duplicate_entity_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}duplicate_entity 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.
Duplicate an entity (and its children) in the current O3DE level. It is categorised as a Write tool in the O3de MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the O3de MCP server in PolicyLayer and add a rule for duplicate_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.
duplicate_entity 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 duplicate_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 duplicate_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.
duplicate_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.