get_scene_view_status

Get comprehensive scene view status

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/get-scene-view-status.md

WHAT IT DOES

What get_scene_view_status does on Cocos

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

This tool retrieves status information about the scene view in the Cocos Creator editor without performing any side effects, modifications, or state changes. It is purely informational and presents no risk of unintended data loss or system damage.

From the tool's definition Tool name 'get_scene_view_status' and description 'Get comprehensive scene view status' indicate data retrieval with no modification. The verb 'Get' and lack of any action verbs suggest read-only querying of the editor's scene view state.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_scene_view_status Allowed

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

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

FAQ

Questions about get_scene_view_status

What does the get_scene_view_status tool do? +

Get comprehensive scene view status. 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 get_scene_view_status? +

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

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

Can I rate-limit get_scene_view_status? +

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

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

get_scene_view_status 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

get_task_status on 0rca Dojo MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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