AI agents use save_level 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.
This tool modifies data by persisting changes to a level file. While the operation is reversible (users can undo or reload), it commits changes to storage and affects the project state. It does not delete or destroy data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely query data (Read). Write category is appropriate for state-modifying operations that create or persist changes.
From the tool's definition The tool 'save_level' explicitly saves the currently open level, which is a write operation that modifies the persistent state of a level file. The description indicates it performs a state-changing operation ('Save the currently open level').
Documented attack patterns abuse exactly the kind of access save_level 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 save_level:
{
"version": "1",
"default": "deny",
"tools": {
"save_level": {
"limits": [
{
"counter": "save_level_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}save_level 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.
Save the currently open 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 save_level: 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.
save_level 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 save_level 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 save_level. 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.
save_level 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.