get_current_scene

Get current scene information

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

WHAT IT DOES

What get_current_scene does on Cocos

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

This tool retrieves scene information from the Cocos Creator editor without creating, modifying, deleting, or executing any operations. It is purely informational and has no ability to alter state or trigger external processes. Low severity due to minimal blast radius if misused by an AI agent—it can only expose existing scene data.

From the tool's definition Tool name 'get_current_scene' and description 'Get current scene information' indicate a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_current_scene Allowed

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

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

FAQ

Questions about get_current_scene

What does the get_current_scene tool do? +

Get current scene information. 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_current_scene? +

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

What risk level is get_current_scene? +

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

Can I rate-limit get_current_scene? +

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

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

get_current_scene 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_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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