Get information about the currently loaded level.
AI agents call get_level_info to retrieve information from O3de without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about a level without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that queries state information from the O3DE editor. The low severity reflects minimal risk from misuse—an AI agent retrieving level information cannot cause harm to the project or environment.
From the tool's definition Tool name 'get_level_info' and description 'Get information about the currently loaded level' indicate data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_level_info 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 get_level_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_level_info": {}
}
}get_level_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get information about the currently loaded level. It is categorised as a Read tool in the O3de MCP Server, which means it retrieves data without modifying state.
Register the O3de MCP server in PolicyLayer and add a rule for get_level_info: 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.
get_level_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_level_info 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 get_level_info. 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.
get_level_info 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.