This record as markdown: /tools/caravanglory-cocos-mcp-server/get-node-info.md
What get_node_info does on Cocos
AI agents call get_node_info 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_info is rated Low
This tool queries and returns information about a scene node identified by its UUID. It performs no modifications, deletions, or external operations—it only retrieves data from the Cocos Creator editor state. The minimal blast radius of a misused Read operation and the clear retrieval semantics justify the 'Read' category and 'low' severity classification.
From the tool's definition Tool name 'get_node_info' and description 'Get node information by UUID' indicate a retrieval operation with no side effects. The verb 'Get' and the action of retrieving information by identifier are characteristic of Read operations.
Attacks that exploit this kind of access
The rule that runs get_node_info 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_info, this is the rule to start with:
get_node_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Cocos, apply this rule, and every get_node_info call is checked against it from then on.
Questions about get_node_info
Get node information by UUID. It is categorised as a Read tool in the Cocos MCP Server, which means it retrieves data without modifying state.
Register the Cocos MCP server in PolicyLayer and add a rule for get_node_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 Cocos. Nothing to install.
get_node_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_node_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_node_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_node_info is provided by the Cocos MCP server (caravanglory/cocos-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cocos, and thousands of servers like it.
This server
Across the catalogue