This record as markdown: /tools/caravanglory-cocos-mcp-server/end-undo-recording.md
What end_undo_recording does on Cocos
AI agents use end_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 end_undo_recording is rated Medium
This tool finalizes/commits an undo recording session in the Cocos Creator editor. It modifies editor state by completing a transaction, making it a Write operation. The recorded changes could be reversed via undo, so it's not Destructive. Severity is low as it merely ends a recording session rather than directly causing significant changes itself.
From the tool's definition End recording undo data
Attacks that exploit this kind of access
The rule that runs end_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 end_undo_recording, this is the rule to start with:
end_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 end_undo_recording call is checked against it from then on.
Questions about end_undo_recording
End 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 end_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.
end_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 end_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 end_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.
end_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