get_node_tree

What get_node_tree does on Cocos

AI agents call get_node_tree to retrieve information from Cocos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_node_tree is rated Low

This tool retrieves and queries the node tree structure from the Cocos Creator editor for inspection and debugging purposes. It has no side effects, does not modify data, and does not trigger external operations. It is a pure read operation with minimal security risk - at worst an agent could inspect internal scene structure but cannot alter or delete anything.

From the tool's definition Tool name 'get_node_tree' and description 'Get detailed node tree for debugging' indicate retrieval of scene/node hierarchy information without modification. Verb 'get' is characteristic of Read operations.

The rule that runs get_node_tree safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Cocos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_node_tree, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_node_tree": {}
  }
}

Questions about get_node_tree