open_build_panel

Open the build panel in the editor

SERVERCocos SOURCEcaravanglory/cocos-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/caravanglory-cocos-mcp-server/open-build-panel.md

WHAT IT DOES

What open_build_panel does on Cocos

AI agents call open_build_panel 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.

RISK

Why open_build_panel is rated Low

Opening a UI panel in the editor is a read/view operation with no data modification or side effects. It merely makes the build panel visible in the editor interface.

From the tool's definition Open the build panel in the editor

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs open_build_panel 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 open_build_panel, this is the rule to start with:

open_build_panel Allowed

open_build_panel is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Cocos, apply this rule, and every open_build_panel call is checked against it from then on.

FAQ

Questions about open_build_panel

What does the open_build_panel tool do? +

Open the build panel in the editor. It is categorised as a Read tool in the Cocos MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on open_build_panel? +

Register the Cocos MCP server in PolicyLayer and add a rule for open_build_panel: 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.

What risk level is open_build_panel? +

open_build_panel is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit open_build_panel? +

Yes. Add a rate_limit block to the open_build_panel 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.

How do I block open_build_panel completely? +

Set action: deny in the PolicyLayer policy for open_build_panel. 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.

What MCP server provides open_build_panel? +

open_build_panel 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.

KEEP EXPLORING

More on Cocos, and thousands of servers like it.

This server

All 157 Cocos tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →