Redoes last undone action
AI agents use redo to create or update resources in Open Brush MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Open Brush MCP Server environment.
Redo is a fundamental write operation that re-applies modifications to the canvas. While it manipulates state, the changes are reversible (via undo), and the blast radius is limited to the current Open Brush project. The severity is low because the effects are easily undone and non-destructive by nature. High confidence reflects the clear reversible nature of redo in any digital application.
From the tool's definition The tool 'redo' restores a previously undone action in Open Brush, which modifies the drawing state reversibly. This is consistent with Write operations that create or modify data.
Attacks that exploit this kind of access
Redoes last undone action. It is categorised as a Write tool in the Open Brush MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Open Brush MCP Server MCP server in PolicyLayer and add a rule for 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 Open Brush MCP Server. Nothing to install.
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 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 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.
redo is provided by the Open Brush MCP Server MCP server (moz411/openbrush-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →