scene · Cocos MCP: Risk & Policy

WHAT IT DOES

What scene does on Cocos MCP

AI agents invoke scene 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 scene needs a policy

Although the description is empty (reducing confidence slightly), the tool's position within a Cocos editor bridge and the server's stated purpose of 'scene manipulation' strongly indicate this tool executes scene graph operations. These are Execute-category because they trigger external operations (editor/engine state changes) whose side effects depend on the arguments passed.

From the tool's definition Tool named 'scene' with empty description on a Cocos Creator editor control server alongside tools like 'execute', 'assets', 'editor'. Context indicates this is part of a 43+ tool suite for 'scene manipulation' in a game engine editor.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scene Rate-limited

scene 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": {
    "scene": {
      "limits": [
        {
          "counter": "scene_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 scene

What does the scene tool do? +

scene. 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 scene? +

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

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

Can I rate-limit scene? +

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

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

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