This record as markdown: /tools/caravanglory-cocos-mcp-server/find-nodes.md
What find_nodes does on Cocos
AI agents call find_nodes 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 find_nodes is rated Low
This tool searches for nodes matching a name pattern in the Cocos Creator scene hierarchy. It is a retrieval operation that queries existing data and returns results without creating, modifying, deleting, or executing anything. The blast radius of misuse is minimal—an agent could only retrieve node information it shouldn't access, which is a low-severity information disclosure risk.
From the tool's definition Tool name 'find_nodes' and description 'Find nodes by name pattern' indicate a search/query operation with no side effects. The verb 'find' is a classic Read operation that retrieves data without modification.
Attacks that exploit this kind of access
The rule that runs find_nodes 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 find_nodes, this is the rule to start with:
find_nodes 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 find_nodes call is checked against it from then on.
Questions about find_nodes
Find nodes by name pattern. 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 find_nodes: 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.
find_nodes 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 find_nodes 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 find_nodes. 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.
find_nodes 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