This record as markdown: /tools/caravanglory-cocos-mcp-server/revert-prefab.md
What revert_prefab does on Cocos
AI agents call revert_prefab to permanently remove resources in Cocos, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why revert_prefab is rated Critical
Reverting a prefab instance discards all local overrides and modifications made to that instance, which cannot be recovered unless the user has an external backup or undo history. This is a destructive, irreversible operation in normal workflow context, with high blast radius if an AI agent accidentally reverts a complex, heavily-modified prefab instance.
From the tool's definition Revert prefab instance to original — 'revert' means discarding all local modifications irreversibly, restoring to the original prefab state and losing any customizations made to the instance.
Attacks that exploit this kind of access
The rule that runs revert_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 revert_prefab, this is the rule to start with:
revert_prefab is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Cocos, apply this rule, and every revert_prefab call is checked against it from then on.
Questions about revert_prefab
Revert prefab instance to original. It is categorised as a Destructive tool in the Cocos MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Cocos MCP server in PolicyLayer and add a rule for revert_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.
revert_prefab is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the revert_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 revert_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.
revert_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.
Across the catalogue