This record as markdown: /tools/airmang-hwpx-mcp-server/undo-last-edit.md
What undo_last_edit does on Hwpx
AI agents use undo_last_edit to create or update resources in Hwpx, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hwpx environment.
Why undo_last_edit is rated Medium
While 'undo' suggests reversibility, the mechanism—replacing the active document with a backup file—is a write operation that modifies the current document state. It is reversible (undo can be undone via redo or further backups), distinguishing it from Destructive category. The high severity reflects that an agent misusing this could revert important edits across a document, causing loss of recent work.
From the tool's definition Tool description states it replaces the current document with a backup from before the last save (마지막 저장 전 .bak 백업과 현재 문서를 교체해), effectively reverting edits. This is a modification operation that alters document state.
Attacks that exploit this kind of access
The rule that runs undo_last_edit safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hwpx, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For undo_last_edit, this is the rule to start with:
undo_last_edit 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 Hwpx, apply this rule, and every undo_last_edit call is checked against it from then on.
Questions about undo_last_edit
마지막 저장 전 .bak 백업과 현재 문서를 교체해 직전 편집을 되돌립니다. It is categorised as a Write tool in the Hwpx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hwpx MCP server in PolicyLayer and add a rule for undo_last_edit: 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 Hwpx. Nothing to install.
undo_last_edit 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 undo_last_edit 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 undo_last_edit. 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.
undo_last_edit is provided by the Hwpx MCP server (airmang/hwpx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hwpx, and thousands of servers like it.
This server
Across the catalogue