restore_prefab_node
Restore prefab node using prefab asset (built-in undo record)
This record as markdown: /tools/caravanglory-cocos-mcp-server/restore-prefab-node.md
What restore_prefab_node does on Cocos
AI agents use restore_prefab_node to create or update resources in Cocos, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cocos environment.
Why restore_prefab_node is rated Medium
This tool modifies editor state by restoring a prefab node, which is a Write operation (creates or modifies data reversibly). It does not delete data (not Destructive), execute arbitrary code (not Execute), involve financial transactions (not Financial), or merely read data (not Read).
From the tool's definition Tool description states 'Restore prefab node using prefab asset' which modifies the state of a prefab node in the editor by restoring it from a prefab asset. The mention of 'built-in undo record' indicates the operation is reversible.
Attacks that exploit this kind of access
The rule that runs restore_prefab_node 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 restore_prefab_node, this is the rule to start with:
restore_prefab_node stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 restore_prefab_node call is checked against it from then on.
Questions about restore_prefab_node
Restore prefab node using prefab asset (built-in undo record). It is categorised as a Write tool in the Cocos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cocos MCP server in PolicyLayer and add a rule for restore_prefab_node: 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.
restore_prefab_node is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the restore_prefab_node 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 restore_prefab_node. 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.
restore_prefab_node 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