scene_snapshot_abort

Abort scene snapshot creation

SERVERCocos SOURCEcaravanglory/cocos-mcp-server

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/caravanglory-cocos-mcp-server/scene-snapshot-abort.md

WHAT IT DOES

What scene_snapshot_abort does on Cocos

AI agents invoke scene_snapshot_abort to trigger actions in Cocos. 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.

RISK

Why scene_snapshot_abort is rated High

Aborting an in-progress operation is an action that triggers an external operation (cancelling an ongoing process) within the Cocos Creator editor. It is not purely reading data, nor is it creating/modifying persistent data or deleting anything irreversibly. It falls under Execute as it triggers an editor control action.

From the tool's definition Abort scene snapshot creation

Attacks that exploit this kind of access

RECOMMENDED RULE

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

scene_snapshot_abort Rate-limited

scene_snapshot_abort 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_snapshot_abort": {
      "limits": [
        {
          "counter": "scene_snapshot_abort_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about scene_snapshot_abort

What does the scene_snapshot_abort tool do? +

Abort scene snapshot creation. It is categorised as a Execute tool in the Cocos 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_snapshot_abort? +

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

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

Can I rate-limit scene_snapshot_abort? +

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

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

scene_snapshot_abort 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 → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →