This record as markdown: /tools/caravanglory-cocos-mcp-server/validate-prefab.md
What validate_prefab does on Cocos
AI agents call validate_prefab 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_prefab is rated Low
Validation is a read-only operation that inspects and checks file format integrity without creating, modifying, deleting, or executing code. The tool retrieves information about file validity but does not alter the prefab or trigger side effects. This is consistent with Read category tools that query or inspect data.
From the tool's definition Tool name 'validate_prefab' and description 'Validate a prefab file format' indicate this performs validation/verification of a prefab file without modifying it or triggering external operations.
Attacks that exploit this kind of access
The rule that runs validate_prefab 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_prefab, this is the rule to start with:
validate_prefab 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_prefab call is checked against it from then on.
Questions about validate_prefab
Validate a prefab file format. 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_prefab: 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_prefab 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_prefab 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_prefab. 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_prefab 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