// MCP TOOL REFERENCE

O3DE TOOLS

30 tools from the O3de MCP Server, categorised by risk level.

// ALL 30 O3DE TOOLS

READ 10 tools

Read get_bus_schema get_bus_schema Read get_capabilities get_capabilities Read get_component_property get_component_property Read get_engine_info Get information about the local O3DE engine installation. Read get_entity_components List all components attached to an entity. Read get_level_info Get information about the currently loaded level. Read list_entities List all entities in the currently open O3DE level. Read list_gems List all external gems registered on this machine. Read list_projects List all O3DE projects registered on this machine. Read list_templates List available O3DE project and gem templates.

WRITE 14 tools

Write add_component Add a component to an entity. Write create_entity Create a new entity in the current O3DE level. Write create_gem Create a new O3DE gem. Write create_project Create a new O3DE project. Write disable_gem Disable a gem in an O3DE project. Write duplicate_entity Duplicate an entity (and its children) in the current O3DE level. Write edit_project_properties Edit properties of an existing O3DE project. Write enable_gem Enable a gem in an O3DE project. Write export_project export_project Write redo Redo the last undone editor action. Write register_gem Register an external gem with an O3DE project. Write save_level Save the currently open level. Write set_component_property set_component_property Write undo Undo the last editor action.

DESTRUCTIVE 1 tools

Destructive delete_entity Delete an entity from the current O3DE level.

EXECUTE 5 tools

Execute build_project Build an O3DE project using CMake. Execute run_editor_python run_editor_python Execute load_level Open a level in the O3DE Editor. Execute enter_game_mode Enter game mode (play-in-editor) in the O3DE Editor. Execute exit_game_mode Exit game mode and return to edit mode.

// FAQ

How many tools does the O3de MCP server have? +

The O3de MCP server exposes 30 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on O3de tools? +

Route the O3de server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do O3de tools fall into? +

O3de tools are categorised as Read (10), Write (14), Destructive (1), Execute (5). Each category has a recommended default policy.

Enforce policy on every O3de tool call.

Start from O3de, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.