reset_node_transform
Reset node position, rotation and scale
This record as markdown: /tools/caravanglory-cocos-mcp-server/reset-node-transform.md
What reset_node_transform does on Cocos
AI agents use reset_node_transform 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 reset_node_transform is rated Medium
Resetting a node's transform (position, rotation, scale) modifies the node's properties back to defaults. This is a reversible write operation (can be undone via undo recording tools available on the server), affecting scene state but not destroying data permanently.
From the tool's definition Reset node position, rotation and scale
Attacks that exploit this kind of access
The rule that runs reset_node_transform 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 reset_node_transform, this is the rule to start with:
reset_node_transform 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 reset_node_transform call is checked against it from then on.
Questions about reset_node_transform
Reset node position, rotation and scale. 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 reset_node_transform: 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.
reset_node_transform 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 reset_node_transform 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 reset_node_transform. 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.
reset_node_transform 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