editor_redo
Re-apply the most recently undone edit in the editor's undo history (like Ctrl-Shift-Z). Defaults to the edited scene's history; pass scope='global' for the editor-wide history.
This record as markdown: /tools/breakpoint-mcp/editor-redo.md
What editor_redo does on Breakpoint
AI agents use editor_redo to create or update resources in Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Breakpoint environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
scope | string | — | Which history to step: 'scene' (default, the edited scene) or 'global' (editor-wide) |
Parameters from the server's own tool schema.
Why editor_redo is rated Medium
This tool re-applies a previously undone edit, which modifies editor/scene state. It is a reversible write operation (can be undone again), making Write the appropriate category. Severity is medium because misuse could restore unwanted changes to a scene, but the effect is reversible.
From the tool's definition Re-apply the most recently undone edit in the editor's undo history (like Ctrl-Shift-Z)
Attacks that exploit this kind of access
The rule that runs editor_redo safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For editor_redo, this is the rule to start with:
editor_redo 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 Breakpoint, apply this rule, and every editor_redo call is checked against it from then on.
Questions about editor_redo
Re-apply the most recently undone edit in the editor's undo history (like Ctrl-Shift-Z). Defaults to the edited scene's history; pass scope='global' for the editor-wide history. It is categorised as a Write tool in the Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
editor_redo accepts 1 parameter: scope. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for editor_redo: 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 Breakpoint. Nothing to install.
editor_redo 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 editor_redo 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 editor_redo. 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.
editor_redo is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue