editor · Cocos MCP: Risk & Policy

WHAT IT DOES

What editor does on Cocos MCP

AI agents invoke editor to trigger actions in Cocos MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why editor needs a policy

Editor control tools in game engine/IDE contexts execute commands that trigger external operations (scene changes, asset modifications, UI updates) whose effects depend on arguments passed to them. This is an Execute classification rather than Write because editor commands typically invoke complex, non-reversible workflows.

From the tool's definition Tool named 'editor' on a Cocos Creator bridge server with 43+ tools for 'scene manipulation, asset management, UI creation, animation, and more'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

editor Rate-limited

editor stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "editor": {
      "limits": [
        {
          "counter": "editor_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Cocos MCP, so you can run agents against it safely.

FAQ

Questions about editor

What does the editor tool do? +

editor. It is categorised as a Execute tool in the Cocos MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on editor? +

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

What risk level is editor? +

editor is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit editor? +

Yes. Add a rate_limit block to the editor 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 editor completely? +

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

editor is provided by the Cocos MCP server (wanghehacker/cocos-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.