Create a new entity in the current O3DE level.
AI agents use create_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.
Creating an entity is a reversible Write operation—it modifies the level by adding a new game object, but the action can be undone (via delete_entity, which is listed as a sibling tool). This is not Read (no data retrieval), not Execute (not running arbitrary code), not Destructive (deletion is separate and entity creation is undoable), and not Financial.
From the tool's definition Tool name 'create_entity' and description 'Create a new entity in the current O3DE level' indicate creation of new data/objects within the editor state.
Documented attack patterns abuse exactly the kind of access create_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 create_entity:
{
"version": "1",
"default": "deny",
"tools": {
"create_entity": {
"limits": [
{
"counter": "create_entity_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_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.
Create a new entity 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 create_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.
create_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 create_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 create_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.
create_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.