scene_snapshot

Create scene state snapshot

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/scene-snapshot.md

WHAT IT DOES

What scene_snapshot does on Cocos

AI agents call scene_snapshot 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 scene_snapshot is rated Low

A snapshot operation captures the current state of the scene for reference or review purposes. This is a read operation with no side effects, similar to taking a screenshot or saving a checkpoint for inspection. Confidence is slightly reduced because 'snapshot' could potentially write a file, but the primary function is reading/capturing state.

From the tool's definition 'Create scene state snapshot' - a snapshot reads/captures current state without modifying it

Attacks that exploit this kind of access

RECOMMENDED RULE

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

scene_snapshot Allowed

scene_snapshot 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": {
    "scene_snapshot": {}
  }
}

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 scene_snapshot call is checked against it from then on.

FAQ

Questions about scene_snapshot

What does the scene_snapshot tool do? +

Create scene state snapshot. 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 scene_snapshot? +

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

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

Can I rate-limit scene_snapshot? +

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

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

scene_snapshot 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 →