This record as markdown: /tools/caravanglory-cocos-mcp-server/validate-scene.md
What validate_scene does on Cocos
AI agents call validate_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.
Why validate_scene is rated Low
The validate_scene tool performs a diagnostic check on the current scene to identify issues. This is a non-destructive, side-effect-free query operation. It retrieves and analyzes scene data to report problems but does not create, modify, delete, or execute external operations. The tool is purely informational and fits the 'Read' category for operations that retrieve or query data without side effects.
From the tool's definition Tool name 'validate_scene' and description 'Validate current scene for issues' indicate a validation/checking operation. Validation is inherently a read-only operation that inspects the scene state without modifying, deleting, or executing arbitrary code.
Attacks that exploit this kind of access
The rule that runs validate_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 validate_scene, this is the rule to start with:
validate_scene is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Cocos, apply this rule, and every validate_scene call is checked against it from then on.
Questions about validate_scene
Validate current scene for issues. It is categorised as a Read tool in the Cocos MCP Server, which means it retrieves data without modifying state.
Register the Cocos MCP server in PolicyLayer and add a rule for validate_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.
validate_scene is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the validate_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.
Set action: deny in the PolicyLayer policy for validate_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.
validate_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.
More on Cocos, and thousands of servers like it.
This server
Across the catalogue