AI agents use create_gem 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 a gem in O3DE is a reversible write operation that adds a new module to a project. While gems are fundamental extensions to O3DE projects and could potentially affect the entire project build and functionality if misconfigured, the operation itself is not irreversible (gems can be removed/disabled) and does not directly execute arbitrary code or delete data.
From the tool's definition Tool name and description indicate 'Create a new O3DE gem' — creating a new software component/module within the O3DE project that can be persisted and integrated into the build system.
Documented attack patterns abuse exactly the kind of access create_gem 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_gem:
{
"version": "1",
"default": "deny",
"tools": {
"create_gem": {
"limits": [
{
"counter": "create_gem_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_gem 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 O3DE gem. 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_gem: 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_gem 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_gem 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_gem. 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_gem 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.