Execute undo in the runner
AI agents invoke ui_undo to trigger actions in UI Bridge MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes an operation (undo) on the runner's UI state. While undo is reversible by nature, it still qualifies as Execute rather than Write because it triggers an external operation whose effects depend on what was previously done (i.e., what state the UI is in). The tool has moderate blast radius if misused in a loop or during critical operations, but is mitigated by being reversible.
From the tool's definition Tool description states it 'Execute[s] undo in the runner', and it is listed among interaction tools on a UI control server that supports interactive control mode. Undo is a reversible state-change operation that executes an action within the runner's own UI.
Attacks that exploit this kind of access
Execute undo in the runner. It is categorised as a Execute tool in the UI Bridge MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the UI Bridge MCP server in PolicyLayer and add a rule for ui_undo: 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 UI Bridge MCP. Nothing to install.
ui_undo is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ui_undo 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 ui_undo. 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.
ui_undo is provided by the UI Bridge MCP server (qontinui/ui-bridge-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 →