This record as markdown: /tools/caravanglory-cocos-mcp-server/begin-undo-recording.md
What begin_undo_recording does on Cocos
AI agents use begin_undo_recording 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 begin_undo_recording is rated Medium
This tool starts an undo recording session in the Cocos Creator editor. It initiates a tracking/recording operation that enables future undo functionality. It modifies editor state by starting a recording session, which is a reversible write operation. The blast radius is low as it only begins a recording session rather than making direct changes to assets or scene data.
From the tool's definition Begin recording undo data
Attacks that exploit this kind of access
The rule that runs begin_undo_recording 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 begin_undo_recording, this is the rule to start with:
begin_undo_recording 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 begin_undo_recording call is checked against it from then on.
Questions about begin_undo_recording
Begin recording undo data. 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 begin_undo_recording: 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.
begin_undo_recording 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 begin_undo_recording 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 begin_undo_recording. 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.
begin_undo_recording 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