unity_undo_last
Revert the most recent undoable MCP action as a whole (create/edit/boolean, not one internal step — each write runs in its own named undo group). With agentId, targets that agent
This record as markdown: /tools/anklebreaker-studio-unity-mcp-server/unity-undo-last.md
What unity_undo_last does on Unity MCP Server
AI agents use unity_undo_last to create or update resources in Unity MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unity MCP Server environment.
Why unity_undo_last is rated Medium
While undo operations modify state, they are reversible and restorative rather than destructive. The tool undoes previous write actions and can itself be undone (implied by MCP undo group semantics), making it a Write category action with low severity since it restores rather than destroys data.
From the tool's definition Tool name 'unity_undo_last' and description explicitly states it reverts/undoes 'the most recent undoable MCP action' — it reverses write operations (create/edit/boolean) that were previously performed, making it a Write operation that restores prior state.
Attacks that exploit this kind of access
The rule that runs unity_undo_last safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unity MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unity_undo_last, this is the rule to start with:
unity_undo_last 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 Unity MCP Server, apply this rule, and every unity_undo_last call is checked against it from then on.
Questions about unity_undo_last
Revert the most recent undoable MCP action as a whole (create/edit/boolean, not one internal step — each write runs in its own named undo group). With agentId, targets that agent. It is categorised as a Write tool in the Unity MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Unity MCP Server MCP server in PolicyLayer and add a rule for unity_undo_last: 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 Unity MCP Server. Nothing to install.
unity_undo_last 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 unity_undo_last 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 unity_undo_last. 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.
unity_undo_last is provided by the Unity MCP Server MCP server (anklebreaker-studio/unity-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Unity MCP Server, and thousands of servers like it.
This server
Across the catalogue